runtime
runtime copied to clipboard
dotnet
Make public surface area of different CoreLibs consistent
In https://github.com/dotnet/runtime/pull/72143 we're adding a reference assembly for System.Private.CoreLib but right now the three different implementations (mono, coreclr and nativeaot) don't have consistent public API.
Tagging subscribers to this area: @dotnet/area-meta See info in area-owners.md if you want to be subscribed.
Issue Details
In https://github.com/dotnet/runtime/pull/72143 we're adding a reference assembly for System.Private.CoreLib but right now the three different implementations (mono, coreclr and nativeaot) don't have consistent public API.
| Author: | akoeplinger |
|---|---|
| Assignees: | - |
| Labels: |
|
| Milestone: | - |
Tagging subscribers to this area: @dotnet/runtime-infrastructure See info in area-owners.md if you want to be subscribed.
Issue Details
In https://github.com/dotnet/runtime/pull/72143 we're adding a reference assembly for System.Private.CoreLib but right now the three different implementations (mono, coreclr and nativeaot) don't have consistent public API.
| Author: | akoeplinger |
|---|---|
| Assignees: | - |
| Labels: |
|
| Milestone: | - |
I wonder how much of a goal it is to make them all exactly consistent, or just all support an intersection of API? cc @jkotas @stephentoub @ViktorHofer
Intersection is good enough. I do not think they need to be exactly consistent. There are good reasons for runtime-specific public surface, one example are runtime-specific hosting APIs.
In that case I'm not sure what this would be tracking since I would expect that to be achieved by creating the contract and committing any baselines.
This issue has been marked needs-author-action and may be missing some important information.
@akoeplinger can you clarify what you think should happen, or close this if you agree with what's said here?
This issue has been automatically marked no-recent-activity because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no-recent-activity.
I think @akoeplinger had in mind resolving warnings like these
MembersMustExist : Member 'protected System.String System.String System.Resources.ResourceManager.BaseNameField' does not exist in the reference but it does exist in the implementation.
or
MembersMustExist : Member 'public void System.AppContext.add_ProcessExit(System.EventHandler)' does not exist in the reference but it does exist in the implementation.
This issue has been automatically marked no-recent-activity because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no-recent-activity.
