Tomas Grosup

Related to https://github.com/dotnet/fsharp/pull/13036/files#diff-89da65b208fb5d835cded7993284e2c562b2d6530cc320cc030f5079dfc0372b possibly?

I think getting an ObjectDisposedException is the right scenario if the object was disposed. But it should be better controlled by Fsharp.Core and not thrown from internal usage.

I agree, 5 versions (v10-v5) of heads-up warning is fair. Also, already released SDK versions will keep their respective compiler supported per the support policy, which gives another level of...

A possible way to get rid of ns20 would be to multitarget FSharp.Core instead. That would however put the burden of doing the same on every library author who wants...

> Perhaps 4 major versions (lining up to 4 years) is a good horizon. Lines up with two .NET LTS versions passing by. Would certainly make sense to me. To...

> Perhaps an RFC or ADR would be in order! Or wherever this kind of stuff may be documented :) > > Just an idea It will be good to...

> Please don't make `mod` a normal identifier. [RFC FS-1114](https://github.com/fsharp/fslang-design/blob/main/FSharp-6.0/FS-1114-ml-compat-revisions.md) explicitly omitted `mod` because of the future possibility of > > * [Addition of a correct modulus operator #1065](https://github.com/fsharp/fslang-suggestions/issues/1065) Makes...

Yes. Anything which requires --langversion:5.0 and/or --mlcompatibility would fall here too, and cleaning it out from the compiler is approved in principle. (for F# 11, only lang versions 11;10;9;8 should...