You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
having the parts or units arranged in a straight line
Inline and line are contextual terms in IT and CS (much like host is).
Even in this case, a line has 2 meanings: a line of text as displayed in the terminal (subject to overflow), and a line as read by the powershell engine when executing statements (terminated by one of powershell's line terminators: \r?\n, ; or })
It's only confusing, if you have ever used the term in one context.
Consider the following:
In most programming languages, this type of statement is considered in-line as the entire thing is evaluated as a singular unit terminated by that language's line endings:
$value= (& {
"Despite this scriptblock taking multiple lines of space,""it is all contained within the wrapping parenthesis,""and terminated by the following colon"
}); # <- the actual line-terminator as interpreted by PowerShell
or in javascript, the IIFE pattern:
varvalue=(()=>{return["Despite this function taking multiple lines of space,","it is all contained within the wrapping parenthesis,","and terminated by that last colon"];})();// <- the actual line-terminator as interpreted by JS
The engine may see IIFE-esque patterns as multiple lines, but the entire encapsulating statement is evaluated as a single line
I've opened an official RFC with the -@ splat parameter approach PowerShell/PowerShell-RFC#397. I've set a request for comments by 2025-09-30 so hopefully we can get some feedback from the WG around the proposed approach.
I've also created a POC PR for people to play around with and validate that the proposed approach is doable in PowerShell #25821.
Activity
-Splatparameter #25574 as a duplicate of this issueanonhostpi commentedon Jul 2, 2025
BEFORE we get into any disagreements:
I'm gonna say it once more (to prevent the exact same conversation that kicked off in the RFC):
I think that we would all be happy if there was anyway to inline splat than no way at all...
iRon7 commentedon Jul 4, 2025
anonhostpi commentedon Jul 5, 2025
Inline as defined by Merriam-Webster's dictionary is a word on its own:
Inline and line are contextual terms in IT and CS (much like host is).
Even in this case, a line has 2 meanings: a line of text as displayed in the terminal (subject to overflow), and a line as read by the powershell engine when executing statements (terminated by one of powershell's line terminators:
\r?\n,;or})It's only confusing, if you have ever used the term in one context.
Consider the following:
In most programming languages, this type of statement is considered in-line as the entire thing is evaluated as a singular unit terminated by that language's line endings:
or in javascript, the IIFE pattern:
The engine may see IIFE-esque patterns as multiple lines, but the entire encapsulating statement is evaluated as a single line
jborean93 commentedon Aug 5, 2025
I've opened an official RFC with the
-@splat parameter approach PowerShell/PowerShell-RFC#397. I've set a request for comments by 2025-09-30 so hopefully we can get some feedback from the WG around the proposed approach.I've also created a POC PR for people to play around with and validate that the proposed approach is doable in PowerShell #25821.