-
Notifications
You must be signed in to change notification settings - Fork 794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--langversion parser is culture-dependent #7757
Comments
Notably, the following works, too: $ dotnet fsc.exe --langversion:4,700000000000000000000000000000000000000001 Because I don't think it's a good idea to parse the version numbers as floating point values. |
Versions should clearly not be a numeric value. I believe Microsoft adopted Semver, so possible values can include multiple dots and a build string (even though that may not be supported right now by BTW, the same issue happens in the Netherlands and Germany, and I'm sure there are others. |
This should be easy to resolve, though semver doesn't apply to language versioning. |
I assume that you would want to use |
As one can think off, this happens also with F# in Visual Studio 2019 (16.3.9) and German Windows. Obviously |
Repro steps
Create a new F# project:
dotnet new console -lang F#
Add
<LangVersion>
to the project:Now, try to build the project:
It seems to be linked with my machine's Russian culture (which uses decimal comma instead of decimal point).
Known workarounds
Use
<LangVersion>4,7</LangVersion>
(yes, with a comma!) — but please never do that, it's totally not portableAdditional info
It's not a
dotnet build
issue, the same happens if I directly invokedotnet fsc.exe
:Related information
The text was updated successfully, but these errors were encountered: