@ramin_hal9001 (though I realized 5 minutes ago that it is actually easy to use this to provide type information to the editor by simply recording the type-checking procedures in the procedure-properties, so we could at least have as-you-type validation whether the values match the required values)
@ArneBab I have been playing around with monadic code in Guile myself lately, and I can see a fairly easy way to incorporate type checking into my system as well, and you have already given me some ideas here.
What is nice is that if you make use of record types as a kind of Functor, and all of your monadic code constructs functors, and the compiler does constant folding and dead code elimination passes, the optimizer would probably be able to tell right away any time you use a procedure wrapped in the Functor type that a "cond" or "case" expression will always evaluate only along a single branch. So it should be able to eliminate code branches that cannot pass type checking.
But I have more experimentation to do before I can confirm whether this is the case. Also, I don't think those optimizations can apply everywhere, only at top-level declarations. But I could be wrong, it might work in arbitrarily nested closures as well.
Add comment