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
{{ message }}
This repository has been archived by the owner on Feb 4, 2019. It is now read-only.
The official grammar in the PowerShell Language Specification, and the shipping Windows PowerShell v3 parser both allow:
> 1..2..3
If you evaluate it in PowerShell, it will fail (``):
Cannot convert the "System.Object[]" value of type "System.Object[]" to type "System.Int32".
At line:1 char:1
+ 1..1..1
+ ~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [], RuntimeException
+ FullyQualifiedErrorId : ConvertToFinalInvalidCastException
If there is a use for this syntax, I don't know what it is.
It's causing the Pash parser to get confused around multiple arguments to a method:
> [char]::IsUpper("abc", 2) # Produces a false error about expecting `..`
Because chaining array range operators are less important to me than method calls, I'm disabling the former to allow the latter.
The text was updated successfully, but these errors were encountered:
The official grammar in the PowerShell Language Specification, and the shipping Windows PowerShell v3 parser both allow:
If you evaluate it in PowerShell, it will fail (``):
If there is a use for this syntax, I don't know what it is.
It's causing the Pash parser to get confused around multiple arguments to a method:
Because chaining array range operators are less important to me than method calls, I'm disabling the former to allow the latter.
The text was updated successfully, but these errors were encountered: