GeezerVison is showing github.com — Style: Remove space after new keyword in implicitly typed array allocation by daxian-dbw · Pull Request #8505 · PowerShell/PowerShell
Conversation
PR Summary
Remove space after new keyword in implicitly typed array allocation.
654 issues are fixed.
PR Checklist
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dongbo Wang (@daxian-dbw) Recently Jason noted that it makes sense to merge Types_Ps1Xml.cs and TypesV3_Ps1Xml.cs (perhaps some files from FormatAndOutput\DefaultFormatters too). I looked this but there are difficulties for me. The merging may speed up startup.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Ilya (@iSazonov) What do you mean by merging them? Having a single .cs file that contains the type definitions for both? I don't think that alone will affect the perf, so there should be more that Jason wanted.
I did looked at the CPU time trace with the IL assemblies when working on the startup perf, and the huge yield methods in those 2 files does take an outstanding amount of the CPU time, over 2%. But the data is from IL assemblies and thus I'm not sure if it's really an issue with crossgen'ed assemblies. I couldn't generate PDBs for crossgen'ed assemblies.
I haven't contact .NET Core team on the crossgen related issues/questions. I moved to something with higher priority.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Yes, single file. Jason simply mentioned that now there is no reason to have different files. Thanks for clarification about perf.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
I will get back to those huge yield state-machine methods when switching back to the CPU trace analysis work.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Perhaps we could get more win by investigating to Jason's PSMore #7857. I guess that definitely yes at startup.
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Labels
CL-CodeCleanup
Indicates that a PR should be marked as a Code Cleanup change in the Change Log
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|