[WIP] Use interpolated strings by CarloToso · Pull Request #18974 · PowerShell/PowerShell · GitHub

PR Summary

Use interpolated strings with String.Format(), StringBuilder.AppendFormat(), String.Create()

PR Context

PR Checklist

PR has a meaningful title
- Use the present tense and imperative mood when describing your changes
Summarized changes
Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
This PR is ready to merge and is not Work in Progress.
- If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
Breaking changes
- None
- OR
- Experimental feature(s) needed
  - Experimental feature name(s):
User-facing changes
- Not Applicable
- OR
- Documentation needed
  - Issue filed:
Testing - New and feature
- N/A or can only be tested interactively
- OR
- Make sure you've added a new test if existing tests do not effectively test the code changed
Tooling
- I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
- OR
- I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:
  - Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
    (which runs in a different PS Host).
    - Issue filed:
  - Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
    - Issue filed:
  - Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
    - Issue filed:
  - Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).
    - Issue filed:

The code can be insterted in {0}.
(In C# 11 even multilines are supported https://learn.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-11#newlines-in-string-interpolations but we should switch from C# 10 to 11 in our msbuild files.)

Perhaps follow works (or will in .Net 8, or C# 11)

$"0x{payLoadData.AsSpan().Replace("-", string.Empty)}");

Really we should replace all string.Format with string.Create

Follow up PR?

No, current changes haven't value. Idea is to use new API to reduce allocations. There is no string.Format with interpalated string handler. I guess I misled you. Please use string.Create.
(You can find all new APIs with interpolated handlers starting with https://source.dot.net/#System.Private.CoreLib/src/libraries/System.Private.CoreLib/src/System/Runtime/CompilerServices/InterpolatedStringHandlerAttribute.cs,382762ca0bf5bcac,references)

Also please don't change our trace.WriteLine() and other such callsites - this requires changes in the APIs themselves, which is not always easy. See example #18246.

Dbg.Assert is our API. In follow PR we could modernize it to support interpolated string handler and then remove string.Format from such callsites.

The same for StringUtil.Format API.

…mand.cs Co-authored-by: Ilya <darpa@yandex.ru>

We can remove verbatim string literal @. Below I see the same too.

We can use StringBuilder.AppendFormat

The same. And we can remove ToString().

The same. I stop review. Please replace all Format with Create.

I'm still working on it, its [WIP]. I'll change it to draft

ToString() can be removed in interpolated strings.

CarloToso The PR is too large. I suggest to split it by 5-10-15 files.

This PR has 592 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

Label      : Extra Large
Size       : +262 -330
Percentile : 86.4%

Total files changed: 103

Change summary by file extension:
.cs : +262 -330

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

Fast and predictable releases to production:
- Optimal size changes are more likely to be reviewed faster with fewer
  iterations.
- Similarity in low PR complexity drives similar review times.
Review quality is likely higher as complexity is lower:
- Bugs are more likely to be detected.
- Code inconsistencies are more likely to be detected.
Knowledge sharing is improved within the participants:
- Small portions can be assimilated better.
Better engineering practices are exercised:
- Solving big problems by dividing them in well contained, smaller problems.
- Exercising separation of concerns within the code changes.

What can I do to optimize my changes

Use the PullRequestQuantifier to quantify your PR accurately
- Create a context profile for your repo using the context generator
- Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
- Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
- Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
Change your engineering behaviors
- For PRs that fall outside of the desired spectrum, review the details and check if:
  - Your PR could be split in smaller, self-contained PRs instead
  - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

One line was added: +1 -0
One line was deleted: +0 -1
One line was modified: +1 -1 (git diff doesn't know about modified, it will
interpret that line like one addition plus one deletion)
Change percentiles: Change characteristics (addition, deletion, modification)
of this PR in relation to all other PRs within the repository.

Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

Ilya (@iSazonov) You are right this PR is too big, I'll leave it open until until I've finished splitting it, then I'll close it

PR split in 7 parts

CarloToso added 6 commits January 19, 2023 00:43

45 files

78bef76

14 Files

6c02093

10 FIles

09c4665

80 search results left

e205c4f

67 left

cea1464

49 left

f69f74b

CarloToso requested review from Paul Higinbotham (PaulHigin), Steve Lee (SteveL-MSFT), Travis Plunk (TravisEz13), Aditya Patwardhan (adityapatwardhan), Andrew (anmenaga) and Dongbo Wang (daxian-dbw) as code owners January 19, 2023 01:07

ghost assigned Travis Plunk (TravisEz13) Jan 19, 2023

pull-request-quantifier-deprecated Bot added the Large label Jan 19, 2023

CarloToso added 3 commits January 19, 2023 02:10

fix error

ed984ab

fix errors

dcf8085

36 left

af6470f

CarloToso changed the title Use interpolated strings [WIP] Use interpolated strings Jan 19, 2023

fix error

3cf0ffc

Ilya (iSazonov) reviewed Jan 19, 2023

View reviewed changes

fix error

a709f7e

Ilya (iSazonov) reviewed Jan 19, 2023

View reviewed changes

13 left

19b37bf

Ilya (iSazonov) reviewed Jan 19, 2023

View reviewed changes

Comment thread src/Microsoft.PowerShell.Commands.Diagnostics/ImportCounterCommand.cs Outdated

Ilya (iSazonov) reviewed Jan 19, 2023

View reviewed changes

CarloToso and others added 3 commits January 19, 2023 11:56

Update src/Microsoft.PowerShell.Commands.Diagnostics/ImportCounterCom…

86c860d

…mand.cs Co-authored-by: Ilya <darpa@yandex.ru>

start replace string.Format with string.Create

5277d11

fix error

957dd4c

Ilya (iSazonov) reviewed Jan 19, 2023

View reviewed changes

pull-request-quantifier-deprecated Bot added the Extra Large label Jan 19, 2023

CarloToso added 4 commits January 19, 2023 15:49

revert

8a509de

5 files left

29e6d90

Add suggestions

13e7898

StringBuilder.AppendFormat

37fe135

Ilya (iSazonov) reviewed Jan 19, 2023

View reviewed changes

1 file

4a7b460

CarloToso marked this pull request as ready for review January 19, 2023 16:16

remove tostring()

38a3af4

last files

eb6879a

CarloToso closed this Jan 19, 2023

This was referenced Jan 19, 2023

Use interpolated strings 8 #18988

Merged

Use interpolated strings 5b #18996

Merged

Use interpolated strings 5c #18997

Merged

CarloToso deleted the Use-interpolated-strings-2 branch January 21, 2023 13:48

This was referenced Jan 21, 2023

Use interpolated strings 11 #19002

Merged

Use interpolated strings 12 #19003

Merged

Dongbo Wang (daxian-dbw) mentioned this pull request Jan 24, 2023

Revert some of the interpolated string changes #19018

Merged

13 tasks

Andree Renneus (trackd) mentioned this pull request Oct 28, 2023

Group-Object displays dates using a MM/dd/yyyy format regardless of the set culture (PowerShell 7.4 Preview) #20584

Closed

5 tasks

                           CimTestCimSessionContext testCimSessionContext = context as CimTestCimSessionContext;
                           uint sessionId = this.sessionState.GenerateSessionId();
                           string originalSessionName = testCimSessionContext.CimSessionWrapper.Name;
-                          string sessionName = originalSessionName ?? string.Format(CultureInfo.CurrentUICulture, @"{0}{1}", CimSessionState.CimSessionClassName, sessionId);

                                           // at a time => bufferSize.Y == 1. Then, we can safely leave bufferSize.Y unchanged
                                           // to retry with a smaller bufferSize.X.
-                                          Dbg.Assert(bufferSize.Y == 1, string.Format(CultureInfo.InvariantCulture, "bufferSize.Y should be 1, but is {0}", bufferSize.Y));
+                                          Dbg.Assert(bufferSize.Y == 1, string.Format(CultureInfo.InvariantCulture, $"bufferSize.Y should be 1, but is {bufferSize.Y}"));

                           uint sessionId = this.sessionState.GenerateSessionId();
                           string originalSessionName = testCimSessionContext.CimSessionWrapper.Name;
-                          string sessionName = originalSessionName ?? string.Format(CultureInfo.CurrentUICulture, @"{0}{1}", CimSessionState.CimSessionClassName, sessionId);
+                          string sessionName = originalSessionName ?? string.Create(CultureInfo.CurrentUICulture, $@"{CimSessionState.CimSessionClassName}{sessionId}");

		return string.Format(CultureInfo.InvariantCulture, $"{0}> {File}",
		FromStream == RedirectionStream.All ? "*" : ((int)FromStream).ToString(CultureInfo.InvariantCulture));

                           {
                               string payLoadData = BitConverter.ToString(fragmentData.blob, fragmentData.offset, fragmentData.length);
-                              payLoadData = string.Format(CultureInfo.InvariantCulture, "0x{0}", payLoadData.Replace("-", string.Empty));
+                              payLoadData = string.Format(CultureInfo.InvariantCulture, $"0x{payLoadData.Replace("-", string.Empty)}");

                                   }
-                                  parameters.Append(string.Format(CultureInfo.CurrentUICulture, @"'{0}' = {1}", key, parameterList[key]));
+                                  parameters.Append(string.Format(CultureInfo.CurrentUICulture, $@"'{key}' = {parameterList[key]}"));

                               if (result == null)
                               {
-                                  throw new InvalidOperationException(string.Format(CultureInfo.CurrentCulture, "DataErrorInfoValidationResult not returned by ValidationRule: {0}", rule.ToString()));
+                                  throw new InvalidOperationException(string.Format(CultureInfo.CurrentCulture, $"DataErrorInfoValidationResult not returned by ValidationRule: {rule.ToString()}"));

                           }
-                          patterns.Add(string.Format(CultureInfo.InvariantCulture, "(?<{0}>){1}", FullTextRuleGroupName, ValuePattern));
+                          patterns.Add(string.Format(CultureInfo.InvariantCulture, $"(?<{FullTextRuleGroupName}>){ValuePattern}"));

                           {
-                              result.AppendFormat(null, "-Culture '{0}' ", CodeGeneration.EscapeSingleQuotedStringContent(runspaceConnectionInfo.Culture.ToString()));
-                              result.AppendFormat(null, "-UICulture '{0}' ", CodeGeneration.EscapeSingleQuotedStringContent(runspaceConnectionInfo.UICulture.ToString()));
+                              result.AppendFormat(null, $"-Culture '{CodeGeneration.EscapeSingleQuotedStringContent(runspaceConnectionInfo.Culture.ToString())}' ");

[WIP] Use interpolated strings by CarloToso · Pull Request #18974 · PowerShell/PowerShell · GitHub

Uh oh!

[WIP] Use interpolated strings - #18974

[WIP] Use interpolated strings#18974CarloToso wants to merge 23 commits intoPowerShell:masterPowerShell/PowerShell:masterfrom CarloToso:Use-interpolated-strings-2CarloToso/PowerShell:Use-interpolated-strings-2Copy head branch name to clipboard

Conversation

CarloToso commented Jan 19, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Summary

PR Context

PR Checklist

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Ilya (iSazonov) Jan 19, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Ilya (iSazonov) Jan 19, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Ilya (iSazonov) commented Jan 19, 2023

Uh oh!

pull-request-quantifier-deprecated Bot commented Jan 19, 2023

What can I do to optimize my changes

How to interpret the change counts in git diff output

Uh oh!

CarloToso commented Jan 19, 2023

Uh oh!

CarloToso commented Jan 19, 2023

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

[WIP] Use interpolated strings#18974
CarloToso wants to merge 23 commits into
PowerShell:masterfrom
CarloToso:Use-interpolated-strings-2

CarloToso commented Jan 19, 2023 •
edited
Loading

Ilya (iSazonov) Jan 19, 2023 •
edited
Loading

Ilya (iSazonov) Jan 19, 2023 •
edited
Loading