为何PowerShell函数不支持带类型的命名[ref]参数？

Great question! This is indeed a quirky behavior in PowerShell's parameter binding system, and you're right to suspect it's a bug (or at least an unpolished edge case in the parser logic). Let's break down what's happening here:

What's causing the issue? #

When you declare a parameter like [ref][string]$message, PowerShell's parser struggles to correctly interpret the combined type annotation during named parameter binding. Here's why:

• The syntax [ref][string] is intended to indicate that the [ref] wrapper contains a [string] value. However, the parameter binding logic doesn't properly recognize this combined type when you use a named argument like -message ([ref]$message).
• In contrast, positional arguments bypass the named parameter matching step—they're bound by position alone, so the parser doesn't get tripped up trying to reconcile the combined type with the parameter name.

When you simplify the declaration to [ref]$message, the parameter type is explicitly just [ref], which the named parameter system can handle cleanly, hence why that works.

Workarounds to use named parameters with typed [ref] #

If you need both type safety and named parameter support, here are two reliable workarounds:

1. Use the generic [ref] syntax
   Declare your parameter with the generic type notation [ref[string]] instead of chaining attributes:

   function GetMessage {
       Param ( [ref[string]]$message )
       if ($message) { $message.Value = 'Hello' }
   }
   
   $message = 'ERROR'
   GetMessage -message ([ref]$message)
   $message  # Outputs 'Hello'
   

   This explicitly tells PowerShell the wrapped type, and the parser correctly maps the named parameter.

2. Validate the type inside the function
   Stick with the simpler [ref]$message declaration, then add a check inside the function to ensure the wrapped value is a string:

   function GetMessage {
       Param ( [ref]$message )
       if ($message -and $message.Value -is [string]) {
           $message.Value = 'Hello'
       } else {
           throw "Parameter 'message' must be a [ref] to a string."
       }
   }
   
   $message = 'ERROR'
   GetMessage -message ([ref]$message)
   $message  # Outputs 'Hello'
   

   This keeps named parameter support while enforcing your type requirement.

Is this a bug? #

Yes, this is widely considered a bug in PowerShell's parameter parsing logic. The issue has been discussed among PowerShell maintainers, who acknowledge that the combined [ref][type] syntax isn't properly handled for named parameters—it's likely an oversight in how the parser processes chained type attributes for ref parameters.

内容的提问来源于stack exchange，提问作者andiDo