Sergio Pedri

> "Using IO to effectively just load data you are shipping is likely less of a problem" @CyrusNajmabadi Sure, and in fact that's what we're currently doing, but it's still...

Picking this up now that 17.4 is mostly done, have we reached a conclusion on what the correct approach (if any) should be used to solve this issue? To recap,...

Just trying to understand this better. Consider this example (using explicit `this` for clarity): ```csharp ref struct ByteContainer { public byte B; public static void GetSpan(ref ByteContainer @this, out Span...

Ah, gotcha, yeah that makes perfect sense. And yeah to be clear, this wasn't meant to "bump" this issue at all, I really just wanted to understand this better and...

I'm very interested in this feature. In [ComputeSharp](https://github.com/Sergio0694/ComputeSharp), I'm adding the ability to annotate shaders so that they can be compiled at build-time and directly embedded into the consuming assembly....

> "The Visual Studio UI must not block on the completion of source generators for any feature. If you see any delays after converting to incremental source generators, it would...

Additionally: I would still like this code to only ever run on actual builds, as it would greatly reduce the amount of times the native binaries are copied to `%TEMP%`,...

Question: what would the UX be in Visual Studio? Specifically, if I have a node that then has both `RegisterReferenceSourceOutput` with just an empty skeleton, and `RegisterImplementationSourceOutput` with the full...

This would be really nice to have. I also hit this same limitation in PolySharp the other day, where I wanted to emit some diagnostics for incorrect MSBuild properties being...

This looks awesome! 😄 > "I think the same could be applied to partial members so that generators won't need to bother duplicating every detail." Had the same thought -...