Tomas Grosup

@copilot : Continue fixing the encountered problems. You have very likely "tested" the standalone version wrong, by using the installed SDK instead of using the freshly built compiler. A good...

@copilot ## ❌ Build / Test Failures ### 💥 Issues - Bash exited with code '1'. — Linux/Build / Test MacOS/Build / Test - Cmd.exe exited with code '1'. —...

Another issue with runtime error caused by the witness (which is only needed for quotations, not for the regular run). The issue can be fixing by targeting the wrong IL...

What was this projects TargetFramework before? Did you update your SDK to dotnet10, TargetFramework to dotnet10, or both? In particular, does having TargetFramework=9 while keeping your net10 SDK work? (the...

Should there be an alternative builder for WASM that avoids problematic API calls? A library replacing the built in one?

I think it's two aspects: - We have a universal try/catch which sends watson error telemetry on any error. This must exclude cancellation. - We do have aggregate wrappers (Task.WhenAll...

Similar to this maybe: https://github.com/dotnet/roslyn/blob/1f78742862ecc35c37de5020e3dd4ce3f7213e66/src/Features/Core/Portable/ExternalAccess/UnitTesting/SolutionCrawler/UnitTestingWorkCoordinator.UnitTestingIncrementalAnalyzerProcessor.cs#L233

What is the rationale for `unit` returning vs. inferred return type (just like `failwith` has) ?

Had another thought about it, and I am not sure if a function is strictly superior - it would limit the placement of `warning ".."` as opposed to using a...

I think it makes sense to support the following three, which also work in C# (without the double quotes there): `#error "message"` `#warning "message"` `#error version` As directives during pre-processing,...