Tomas Grosup

I am thinking of some sensible real-world-like usecase involving a builder. If anyone has an idea, I can definitely put it together as a test case (in this case, one...

Thank you @ijklam , this looks good. Please follow https://github.com/dotnet/fsharp/blob/e4950e6c3f4f7e9829dd86f127a0e7cf54d9220e/DEVGUIDE.md?plain=1#L266 to verify and update the ilverify baselines, since some changes have been detected for this PR. I will review this...

I propose to merge this in as is with the `#line` limitation, afterall it is a construct for code generators. This PR does come under a LanguageFeature flag and we...

> Majority of issues were due to parallel resolution it seems. Still doesn't explain why do I have weird issues in tests locally, but not in CI. > > It's...

@DedSec256 : Interface implementation can have attributes on it (not expressible in F#/C#, but in IL it is) and C# nullness metadata export makes use of it. The nullness PR...

Alex @DedSec256 , can I move it out of draft now that all is passing?

Thanks for the finding, this makes sense. The workaround/recommendation until then would likely be to use the `string` function.

I (think I) did support for consumption of "nullable-affecting overrides", they are present in the BCL and I encountered it already. The consuming side is there. This issue is right...

@kerams : I am trying to publish a valspec for modified ToString (returning a string without null), but the possibility of overrides coming **after** usage makes this trickier than I...

I think there are two perspectives: 1. Admit that with downcasting, the code is inherently dangerous at runtime. i.e. allow downcasting e.g. a nullable obj into a DU 2. Try...