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
Enable -- warning for mismatched param names by default in new desktop templates and the netsdk #3539
Comments
Can we please add a single parameter (maybe Then I would add this one to all my project files. Roslyn has something similar |
Yes I think typescript has something similar with the contract that you opt in new stuff automatically (and might break you). |
@0x53A I sort of like it ... How do you propose that we treat warnings that added in the future? is strict always strict and always getting tougher and tougher? |
Yes. Strict means my code may break at any compiler update. Otherwise we would need --really-strict and --really-truly-strict at later points ;-) Roslyn also "fixes" other compiler bugs in strict mode: https://github.com/dotnet/roslyn/search?q=FeatureStrictEnabled&type=Code&utf8=%E2%9C%93 |
I just chatted with @jaredpar. feature strict enables an ECMA compliance check. but we have an option: --warnon:<warn;...> Perhaps if we enabled: |
I don't remember one at the top of my head, but I think there were a few noisy warnings which are off by default on purpose and not due to backwards compatibility. In contrast, I imagine |
@0x53A ... yes I can see that ... so --warnon:strict to enable the stricter warnings for all of the stuff we turn on in the templates. Sound like a plan? |
Sounds good |
👍 from me |
This PR: #3527 adds a warning for mismatched param names between signatures and implementations.
As a change it's highly breaking as so is not enabled by default in the compiler.
This issue asks to:
.... yes it's a break, but those projects should be fresh and should be fixed.
The text was updated successfully, but these errors were encountered: