4 ms·
Wow, and I was just looking at mixing this in with a API C# dotnet core app I was playing with. Wish it was easier to mix the two, it's pretty nice being able
by month13 8y ago
Wow, and I was just looking at mixing this in with a API C# dotnet core app I was playing with.
Wish it was easier to mix the two, it's pretty nice being able directly interface through dotnet, be even better if I could have fs and cs files next to each other.
- sparkie 8y agoOne thing about F# is that the ordering of compilation units is essential. You need to list your files in the order they are to be compiled because you cannot have circular dependencies between the units. This leads to making better decisions about code most of the time. It is still possible to have circular dependencies. Either by including the mutually related types in the same code file separated by the "and" keyword, or by using signature files to define the type signatures ahead of their implementation (which work similar to header/implementation files in C, C++ etc).