-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Remove CheckForOverflowUnderflow #63725
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsI think this can be removed runtime/src/libraries/Directory.Build.props Lines 90 to 91 in 4d97cda
|
Thanks, @deeprobin I think we are referencing that issue on the code as a historical context on why we disabled it globally. We tried to enable it for some time but then disabled it. The comment says we decided to keep it disabled by default, @stephentoub do you happen to know why did we decide to turn this off again? |
Because we don't want it enabled. The vast majority of code expects it to be off and it would be a sheer ton of busy work to reliability find and change all the places that depend on it. And at that point, you've either cluttered up the code with lots of ifdefs to handle only having it enabled in debug, or you've added run-time cost to also have it enabled in release. We don't want any of that :) That said, the default is false, so I'm not sure why it's needed in the Directory.Build.props, unless we're concerned about it being flipped somewhere higher up. |
Thanks, @stephentoub :). From a quick GH search for the property that is the only place we have it set, so there is nowhere higher up flipping it on: https://github.com/dotnet/runtime/search?q=CheckForOverflowUnderflow I think we can safely remove it. |
I think this can be removed
runtime/src/libraries/Directory.Build.props
Lines 90 to 91 in 4d97cda
The text was updated successfully, but these errors were encountered: