Jared Parsons

> https://github.com/dotnet/csharplang/pull/7906: developers can add weight to which methods are better in overload resolution. This seems unlikely to impact F# as much. Want to point out one place this will...

> Something I've been thinking about recently is that source generators should be disabling warnings altogether in generated code, since they're not actionable at all when surfaced to users. They're...

> Why shouldn't the source generator be able to disable warnings on things it itself is generating? I don't have any issues with generators suppressing specific warnings. I do have...

> . I don't see much of a point in production builds - Consider this exact bug as an example of why we should be emitting in production builds. There...

Imagine the warning is coming from a security based analyzer. Automatically suppressing that just because it's generated code is almost certainly the wrong move and would result in uncomfortable conversations.

For obsolete / experimental specifically I was mulling over whether we should consider a named group suppression (as detailed in [73292][pragma]). ```csharp #pragma warning disable obsolete #pragma warning disable experimental...

Does anyone know why the determinism settings are turned off? All determinism does in the compiler is ensure that 1. A deterministic MVID is produced 2. A deterministic timestamp is...

@slang25 sorry been a bit behind. Changes look good!

> One point that is not immediately clear to me is how to get hold of the syntax trees produced by source generators. Is there a Roslyn API that would...

> Yes, this is the goal. Okay will add an API for that https://github.com/jaredpar/complog/issues/125 > BTW, what is the reason that Roslyn doesn't expose an API on CSharpCompilation to run...