Use params.useExceptions instead of betterC to gate generation of try/catch in ctors #15357
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In DMD,
-betterC
is the mechanism that controls this individual feature setting, it should not be the gauge as to whether nothrow violating code should be generated or not.This almost allows the entire front-end to be built with
-fno-exceptions
. The one remaining place that falls foul is a scope(failure) in semantic2 that shouldn't be there.