ISourceGenerator should have async methods

[springy76]

Please don't repeat the same design error as aspnetcore1.0 did with the unmodified IFileProvider imported from Owin/Katana.

[jcouv]

FYI @chsienki

[chsienki]

The ISourceGenerator methods are synchronous by design. Generators shouldn't be doing any I/O bound work: the reading of files etc should be handled by the compiler itself, and the generator just accesses the contents.

I'm going to close this as by-design, but feel free to add comments if there are scenarios that you think can only be achieved with async.

[as-ivanov]

Hi @chsienki,

I'm going to close this as by-design, but feel free to add comments if there are scenarios that you think can only be achieved with async.

What if I need to generate, say, a typescript or json-schema file based on my C# code? In case source generators (or analyzers) had async flow, async I/O could be utilized for that.
From the other hand source generators do not provide any API for generating arbitrary files. Do you have an intention to support possibility of generating arbitrary content in future?

[CyrusNajmabadi]

Do you have an intention to support possibility of generating arbitrary content in future?

No, there is no intention to support that.