Proposal for inline splatting

Summary of the new feature / enhancement

Sometimes I just declare a temp variable used for nothing else other than for splatting a function call:

$p = @{a=1;b=2;c=3}
Some-Func -AdditionalParam 4 @p -AnotherParam 5

However, I do this as a means of dealing with the fact that PowerShell does not have a way to do inline splatting.

I propose the following syntax:

Some-Func @:@{a=2;b=2;c=3}                             # Functions
& "somescript.ps1" @:@{d=4;e=5;f=6}                    # Script files
& $someScriptBlock @:@{g=7;h=8;i=9}                    # Script blocks
& $somePSObject.SomeScriptMethod.Script @:@(1,2,3,4,5) # Script methods

Proposed technical implementation details (optional)

No response

Another consideration for those who prefer array splatting:

& $someScriptBlock @:@( 1,2,3 )

Some-Func @:(&{
    $externalValue1
    Generate-MeSomeValues
    @( 1,2,3 )
})

Indeed, inline splatting would be nice.

This was first proposed a long time ago:

Rejected RFC: https://github.com/PowerShell/PowerShell-RFC/blob/master/Archive/Draft/RFC0002-Generalized-Splatting.md
- Related discussion: RFC0002-Generalized-Splatting comments PowerShell-RFC#6
A related PR that was therefore ultimately not accepted: Add @@ syntax for inline splatting as hashtable as new experimental feature PSGeneralizedSplatting #10073

GitHub
PowerShell-RFC/Archive/Draft/RFC0002-Generalized-Splatting.md at master · PowerShell/PowerShell-RFC
RFC (Request for Comments) documents for community feedback on design changes and improvements to PowerShell ecosystem - PowerShell/PowerShell-RFC

Is there a process to request that a RFC be revisited or re-opened?

I understand that there was conflict with which method should be used, but honestly, I'd just be happy with any method over no method at all

Speaking in no official capacity whatsoever:

My personal sense is that the RFC process is all but dead (as of this writing, there are no drafts except an accepted one that submitted in 2022 and has not been implemented since).

I suspect that in practice feature requests have taken their place, if they get tagged for review by the relevant WG (working group).

I've lost track of the original discussion and why the proposal was rejected.
If you feel inspired, you could try to summarize the old debate here and make a case for your proposal in relation to it.

I'm attempting to take another stab at splatting enhancements in PowerShell and have opened a summary of the various options proposed over the years and am hoping to get feedback from anyone interested. If you are interested in having a look and/or wanting to comment on some of the options I would love any feedback at jborean93/PowerShell-RFC#1.

The aim is to get more community consensus around the various options before settling on a real RFC based on the feedback and going from there.

Centralizing all of the issues about inline splatting in #25721

Blue Falcon (@anonhostpi)

📣 Hey @Blue Falcon (@anonhostpi), how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Microsoft Forms

Navigation Menu

Repository navigation

Proposal for inline splatting #25029

Summary of the new feature / enhancement

Proposed technical implementation details (optional)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Proposal for inline splatting #25029

Description

Summary of the new feature / enhancement

Proposed technical implementation details (optional)

Activity

anonhostpi commented on Feb 15, 2025

mklement0 commented on Feb 15, 2025

mklement0 commented on Feb 16, 2025

anonhostpi commented on Feb 20, 2025

mklement0 commented on Feb 20, 2025

jborean93 commented on May 27, 2025

SeeminglyScience commented on Jul 2, 2025

microsoft-github-policy-service commented on Jul 2, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions