-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Garbage collect CoreLib resource strings #46121
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Most seem to be orphaned after the deletion of Utf8String and built-in WinRT support.
05595e4
to
a487b17
Compare
I re-ran the script (the one that Stephen created/ran a couple years ago), including Mono this time too. I manually excluded resources that are dynamically computed here:
|
@stephentoub @danmosemsft could you have a look? |
@MichalStrehovsky could you stick the script here or a gist for it, for future use? Ideally we would eliminate the places we dynamically construct resource ID's in our tree, then we could trivially run this periodically on the tree. It was not hard to find other dead strings earlier this week, eg. #46186 |
It was this one: dotnet/coreclr#18808 (comment) I just copied Mono's CoreLib into CoreCLR's directory and I have the symbolic links described here as well: Lines 343 to 351 in fcf0b8b
|
Most seem to be orphaned after the deletion of Utf8String and built-in WinRT support.