Monad of no `return` Proposal (MRP): Moving `return` out of `Monad`
Imants Cekusins
imantc at gmail.com
Fri Oct 2 21:38:07 UTC 2015
speaking not about this particular "return" issue but change as such:
change can be
a) avoided or
b) accommodated.
let's think of abstract languages L and N. Any resemblance is
coincidental and irrelevant.
Suppose that:
a significant codebase written in L is available
N is a new language with few libraries
a beginner programmer A.B. considers to dedicate their time and effort
to either L or N
A.B. prefers (for various reasons) N syntax.
an experienced programmer C.D. dedicated their time to L language.
C.D. is comfortable with L, wrote and use L code. C.D. can see some
advantages language N gives over L.
the number of programmers similar to C.D. (the L crowd) is fairly
stable but who knows: C.D. may join the N crowd.
number of A.B. and other undecided programmers varies. The more are
A.B.'s, the larger is future camp of any language: L, N, ...
let's think. This is not to argue pro/con but to put things in
perspective. If you were in A.B.'s shoes, what would you do?
More information about the Libraries
mailing list