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

could and might #4319

Closed
35 tasks done
zygoloid opened this issue Nov 9, 2020 · 4 comments
Closed
35 tasks done

could and might #4319

zygoloid opened this issue Nov 9, 2020 · 4 comments
Milestone

Comments

@zygoloid
Copy link
Member

zygoloid commented Nov 9, 2020

ISO wants us to avoid "could" and "might" appearing anywhere in the document. TODO list:

  • Front matter + Clauses 1, 2, 3 -- no changes
  • 4 General principles[intro] -- no changes
  • 5 Lexical conventions[lex] -- jmaurer
  • 6 Basics[basic] -- jmaurer
  • 7 Expressions[expr] -- jmaurer
  • 8 Statements[stmt.stmt] -- jmaurer
  • 9 Declarations[dcl.dcl] -- jmaurer
  • 10 Modules[module] -- no changes
  • 11 Classes[class] -- jmaurer
  • 12 Overloading[over] -- jmaurer
  • 13 Templates[temp] -- jmaurer
  • 14 Exception handling[except] -- jmaurer
  • 15 Preprocessing directives[cpp] -- jmaurer
  • 16 Library introduction[library] -- jmaurer
  • 17 Language support library[support] -- jmaurer
  • 18 Concepts library[concepts] -- jmaurer
  • 19 Diagnostics library[diagnostics] -- jmaurer
  • 20 General utilities library[utilities] -- jmaurer
  • 21 Strings library[strings] -- jmaurer
  • 22 Containers library[containers] -- jmaurer
  • 23 Iterators library[iterators] -- jmaurer
  • 24 Ranges library[ranges] -- jmaurer
  • 25 Algorithms library[algorithms] -- jmaurer
  • 26 Numerics library[numerics] -- jmaurer
  • 27 Time library[time] -- jmaurer
  • 28 Localization library[localization] -- jmaurer
  • 29 Input/output library[input.output] -- jmaurer
  • 30 Regular expressions library[re] -- jmaurer
  • 31 Atomic operations library[atomics] -- jmaurer
  • 32 Thread support library[thread] -- jmaurer
  • Annex A (informative) Grammar summary[gram] -- no changes
  • Annex B (informative normative) Implementation quantities[implimits] -- no changes
  • Annex C (informative) Compatibility[diff] -- jmaurer
  • Annex D (normative) Compatibility features -- jmaurer
  • Back matter -- no changes

Please add your name next to a section to claim it, and check the box when it's done.

@JohelEGP
Copy link
Contributor

Consider following @jensmaurer approach of using "possible" to replace "might", as shown in #4334, to maintain consistency.

@jwakely
Copy link
Member

jwakely commented Nov 11, 2020

Some of the "it is possible" rephrasing feel awkward when involving a negation. For example, "It is possible for f not to be called at all,".

Similarly "It is possible for line #1 not to result in concurrency" later in the same pull request.

I don't have better suggestions for those ones right now.

@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 11, 2020

Do let us keep those awkward fixes in a separate pile, for C++20 only, and we'll revisit those later.

@jensmaurer
Copy link
Member

C++20 has shipped.

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

No branches or pull requests

5 participants