Phillip Carter
Phillip Carter
> The advantages of making this adjustment to F# are that we can use FSI for scripting. Could you clarify what you mean here? Executing F# code in blocks sent...
@mlaily I won't speculate here - the answer to "where is startup time being spent?" is going to differ from script to script and environment to environment. It would be...
I don't have too much to add here, but regarding this: > it feels orthogonal to fsi's purpose to cache assemblies on disk. The purpose of software is always up...
Another thing to consider here is letting FSI take part in a compiler server system that was prototyped a few years ago. Some discussion here: https://github.com/dotnet/fsharp/discussions/11134#discussioncomment-392397 It does not help...
I think it's worth a quick survey of some languages with a good learning curve and what all they do: **Python** `print("yeet")` -- prints `"yeet"` and a new line `print("yeet",...
In general I'm in favor, though I could see this as being by design from @dsyme's perspective.
We don't have one figured out yet. History doesn't provide a good guide either, since releases could be days apart of several months apart. I think we'll want to consider...
@matthid this is mentioned in the docs for F#. It's definitely got a use case: https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/type-extensions#generic-limitation-of-intrinsic-and-optional-type-extensions
Oh, assembly level attributes. No, nobody uses those.