Gauthier Segay

Note about `$(NoWarn);...`, I think it is almost always better to use `$(WarningsNotAsErrors);...` instead.

> they would pre-scan the code to collect all of the #r nugets It wouldn't work with the `#r "notnuget: "` which currently works in dotnet interactive (and fsi, and...

@KevinRansom, from my standpoint, I liked the idea of fsc compiling scripts, but couldn't put it in practice due to the missing assemblies and manual overhead for packaging, hence I...

@KevinRansom I like your plot, but it probably opens things to consider, with regard to support in IDEs and FCS? Do you also see that DependencyManager infrastructure and extensions would...

@MecuSorin, fair points, albeit, all scripts, in their environment, may have some issues, to turn into full fledged projects, many scripts are IT tasks, and migrating those into full fledged...

There is something which currently makes IL baseline tests not robust among test runs and platform differences, related to static field. ```log $ use_binding_on_struct_enumerator.fsx.il.net472.release.bsl diff at line 92: expected: .field...

Considerations: * would it be better done as a FSI extension through `#r "fsih: List.map"`? * for terminal output, it would be possible to pretty print a bit the output,...

> #r is a dependency manager functionality/extension. And if done via DM, it will be quite verbose and confusing. I concede it might sound unatural, but #r stands for "reference"...

> We should improve the error message here What would it do? leverage the fact that the type defines `op_Implicit` for all branches, and guides the user to use it?

what do we want to do for: ```fsharp [] type T3() = class end ``` It doesn't cause an error, so the suggested error message would not be accurate by...