Gus

@NinoFloris after reading your comments, I'm thinking maybe we should open another suggestion for either allow specifying a default or allow specifying that there's no default. Or maybe both of...

I'm personally fine with the possibility of shadowing `int`, `string` and I think nowadays it's pretty standard to do so in small function scopes, though I don't do it that...

Actually when I thought about workarounding the limitation of Higher Ranks by passing a type instead of a function, the first thing that came to my mind is to have...

I agree with @njlr but would add that [Fleece](https://github.com/fsprojects/Fleece/tree/master/src/Fleece) offer those same advantages and more (plus it has better performance) only Fable compatibility is still pending at the time of...

No, I don't have those errors when compiling. Also you can check on [myget](https://www.myget.org/BuildSource/List/gusty) it compiles and run all tests.

Mine is: - AssemblyVersion("4.3.1.0") - AssemblyFileVersion("4.31.21005.1") So probably there was a breaking change. Anyway I remember having tested the whole project with the coming F# 4.0 and worked fine.

Thanks. May be we should send a report to the F# guys. But then we should try to isolate the code that throws the error from the rest of the...

I get the same errors if I compile in DEBUG mode. Can you try to compile it in RELEASE?

This was implemented [here](https://github.com/gmpl/FsControl/commit/5ae4779050528b6f1183fb4f0447360664c53c0b). But note that the default definition uses the lazy signature ``let delay x = x()`` even for non-lazy monads like list or array which in theory...

After the merge with FSharpPlus this issue will be tracked [here](https://github.com/gmpl/FSharpPlus/issues/32). And now I see a problem with the always-delayed approach, see the code example there.