Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Range operator (aka DotDot operator) with char operands in pipeline throws error #5519
Steps to reproduce
Cannot convert value "A" to type "System.Int32". Error: "Input string was not in a correct format."
I see - that very nonstandard name is the reason that I wasn't able to find this new feature, despite then already knowing that it exists (based on this issue - that someone else would call it "DotDot operator" too hadn't occurred me), so thank you for adding the link.
I guess my mentioning the construct's official name here - range operator - now makes this issue more discoverable and, by extension, now also the linked PR, but my preference is always to have the important keywords in the title, as an
The output from
Why, I'm not entirely certain yet, will keep digging. While this is certainly not the intended behavior of the new
Re: the "nonstandard" name, I took it from the token that represents the underlying range operator :-)
changed the title from
DotDot operator with char operands in pipeline throws error
Range operator (aka DotDot operator) with char operands in pipeline throws error
Nov 21, 2017
@SteveL-MSFT: Your title edit just made my day, thanks (I wish I were kidding).
@IISResetMe: Fair enough, and perhaps "DotDot operator" is reasonably well-known; my term for it came from
Operators should be named for their purpose (only), not their syntactic form (too).
I won't repeat my rant about about the "dot sourcing operator" here.