-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Many members of System.Ref.Emit missing #7636
Comments
Any plans for the closing the gaps mentioned? Specifically looking at missing members on |
These are currently missing and are needed for compiling regexes to an assembly. (AppDomain.DefineDynamicAssembly is also missing but replacable with AssemblyBuilder.DefineDynamicAssembly) |
@atsushikan would it be feasible to bring the above mentioned APIs back? I haven't yet looked at them so I don't know if there's a technical reason for not implementing them. |
Non-trivial. Reflection.Emit that saves to disk would need significant amount of work for .NET Core.
Yes, there is a technical reason: Reflection.Emit works against implementation assemblies. The assemblies that it would produce would reference S.P.CoreLib and other internal implementation assemblies that we do not maintain surface compatibility for. |
Is this something we have planned for future or completely out of scope? Thanks Jan! |
https://github.com/dotnet/corefx/issues/4491 is sufficient |
Incomplete System.Reflection.Emit: https://github.com/dotnet/coreclr/issues/10199
The following members are on types implemented in .NET Core. However on desktop they have more members. The members below are missing from Core.
The problem with this situation is
These are not part of NS2.0. I didn't look at usage data. Some of these may not be technically possible on Core in which case ideally we'd at least have them present but throw PlatformNotSupportedException. Even if we don't have time to implement them, it's potentially valuable to do that (allows compile to succeed, for a runtime path that may not be followed). This is potentially a 2.0 issue but not necessarily.
The text was updated successfully, but these errors were encountered: