Don Syme
Don Syme
> This is due to changes in the way runtime serialization and appdomains work (@eiriktsarpalis can elaborate more) I think with .NET Standard 2.0 we could revisit this at some...
> Main blocker for a .NET Core move AFAICT is lack of a repl that targets netstandard or netcorepp. It removes the primary appeal for using this. AppDomains can be...
Here's example code that launches the FSI.EXE on .NET Core correctly: https://github.com/Microsoft/visualfsharp/blob/master/tests/scripts/fsci.fsx
For the application I saw, it would be a massive mix of native DLLs, config files, data files, and goodness knows what else. Basically a situation where some native DLLs...
@kxxr I know this is sometime back but if you would like to consider submitting a PR for this it would be most welcome.
@eiriktsarpalis Re Fsi codegen - right, but as I understood from our discussions that comes at the cost of not allowing class-based members to access defined values. So in C#...
IIL can be used targeting any framework, as long as you're compiling with F# 6
@jackmott needs to add fsprojects org as an owner of the package in nuget https://www.nuget.org/packages/SIMDArray/ Or else a new package name is needed - perhaps FSharp.Collections.SIMDArray is OK though we...
My recommendation is to find criteria to reduce the recommendation of >> composition. For example never for operators. Perhaps some other cases too. See my talk "F# Code I Love"...
This should be ready to do now