NN
There was some unfinished work in https://github.com/rsdn/nemerle/tree/retarget-compiler It allows compiling to .NET Core. I don't see currently a future for the language without some sponsorship.
Interesting, I didn't think about active pattern. There is ExtensionPattern macro which can be used together with regular match.
Current Nemerle implementation doesn't allow to make namespace level macro. It means that supporting unions requires compiler change. It is possible to do it using macro-attribute such as: ``` nemerle...
Same for types: ``` nemerle namespace A { class X{} namespace B { class X{} class Q { x : X; // error: type name `X' is ambiguous, it could...
It is easy to fix using same technique of #537 If you willing to fix it, I can tell you where and how.
Nemerle has its own functional type since it is invented before System.Func and System.Action came into play. There is Nemerle.Internal.Function and Nemerle.Internal.FunctionVoid which are represented by syntax typeparams -> returntype...
As you can see in Lexer.n: https://github.com/rsdn/nemerle/blob/master/ncc/parsing/Lexer.n#L1261 You are totally correct. You can help us fixing this code to parse correctly using Int64 and not UInt64 in that case. Don't...
We are doing similar in NemerleWeb. We generate classes from javascript. It is not a technical problem to do the same as in F#.
There is no global type inference for fields on purpose. The reason for this is slowness of the compiler :) List , arrays and others are just special cases. You...