Skip to content
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

ES.61 clarify Enforcement wording #2137

Merged
merged 1 commit into from
Sep 28, 2023
Merged

Conversation

oldnewthing
Copy link
Contributor

The original text was "If the new and the delete are in the same scope, mistakes can be flagged." This has been misinterpreted to mean "Any new and delete in the same scope is a mistake and should be flagged."

Reword the Enforcement clauses to follow the pattern established by the other Enforcement clauses: "Flag (bad thing)". Also, call the issue a "mismatch" rather than a "mistake", so that it is more clear that the underlying issue is the mismatch between scalar and array new/deletion.

The original text was "If the `new` and the `delete` are in the same scope, mistakes can be flagged." This has been [misinterpreted](https://stackoverflow.com/q/75905524) to mean "Any `new` and `delete` in the same scope is a mistake and should be flagged."

Reword the Enforcement clauses to follow the pattern established by the other Enforcement clauses: "Flag (bad thing)". Also, call the issue a "mismatch" rather than a "mistake", so that it is more clear that the underlying issue is the mismatch between scalar and array new/deletion.
@oldnewthing
Copy link
Contributor Author

@cubbimew Sorry, I'm new to this repo. I can't merge this PR myself (no permission). Is there something more I need to do to get this merged in?

@hsutter hsutter merged commit 27e662b into isocpp:master Sep 28, 2023
1 check passed
@hsutter
Copy link
Contributor

hsutter commented Sep 28, 2023

Thanks, Raymond! Sorry for the lag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants