Re: Monad of no `return` Proposal (MRP): Moving `return` out of `Monad`

I find this especially true in light of the recent advances made in the area of tooling. We are now in a much better position to be offering tools for automated refactoring than we were even when we considered AMP.

Well, it's not like this particular proposal requires tools any more sophisticated than cut&paste (for instance declarations) and search&replace (/return/pure/). The only code that will be negatively affected is code that is not maintained or is printed on dead trees. Best regards, Marcin Mrotek