Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Compilation Pipeline #15649

Closed
alrz opened this issue Dec 2, 2016 · 1 comment
Closed

Proposal: Compilation Pipeline #15649

alrz opened this issue Dec 2, 2016 · 1 comment

Comments

@alrz
Copy link
Member

alrz commented Dec 2, 2016

Generators (#5561) allow to add code to the compilation unit and replace/origin (#5292) can replace members at the declaration-site. But still we can't intercept statements or method calls that are potentially outside of the assembly boundaries (e.g. linq calls could be inlined). This is not just about the code itself, one could be able to run an analysis on the code and generate useful information in the resultant xml docs (#15573). I don't know if currently there exists a mechanism to do this. But I'd greatly appreciate it if we could intercept the compilation pipeline and access to all the information that the compiler produces. This could be an alternative to il weaving, except for that it's done before the actual codegen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant