-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[mono] Full support for System.Reflection.Emit #37794
Labels
area-VM-reflection-mono
Reflection issues specific to MonoVM
runtime-mono
specific to the Mono runtime
tracking
This issue is tracking the completion of other related issues.
Milestone
Comments
Dotnet-GitSync-Bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Jun 12, 2020
marek-safar
added
runtime-mono
specific to the Mono runtime
and removed
area-CoreLib-mono
labels
Jun 30, 2020
Changing area to interop-Mono. Please add a "reflection.emit-Mono" area if desired. |
lambdageek
added
area-VM-reflection-mono
Reflection issues specific to MonoVM
Team Epic
and removed
area-Interop-mono
labels
Oct 26, 2020
marek-safar
added
tracking
This issue is tracking the completion of other related issues.
and removed
Team Epic
labels
Jan 29, 2021
26 tasks
Low priority - Moving to Milestone 8.0.0 |
Moving to 9.0.0 |
cc: @ivanpovazan |
This is a tracking issue. individual problems are tracked separately. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-VM-reflection-mono
Reflection issues specific to MonoVM
runtime-mono
specific to the Mono runtime
tracking
This issue is tracking the completion of other related issues.
Mono's support for System.Reflection.Emit must be brought to the same level as CoreCLR's. From the top down, this requires:
Known Issues
dotnet/runtime
:Known issues with sharing code
interface ISymbolWriter
is both tied heavily with coreclr (seeCreateISymWriterForDynamicModule
) and ILGenerator/MethodBuilder.MonoModule
.Discussion
We can share progress/ask questions in the comments.
The text was updated successfully, but these errors were encountered: