[basic.lookup.general] Italicise "follow" in [basic.lookup.general]/2#8400
Conversation
|
As Brian suggested, I think adding a note that states it clearly would be nice as well. Not sure if that's the right call so I'll hold on with this one for now. |
|
@TymianekPL , if you want the git change history to show your full name, please configure it in github. |
This one? |
|
Ah okay, you mean the name thing |
|
OK. There's a wider issue that ISO doesn't really want things italicised, and that all definitions must come from Clause 3, but that's not really practical for us. But this does mean that we have routinely created "local definitions" that are not marked up typographically and are not indexed. (I think "empty" as the shared pointer state comes to mind: https://eel.is/c++draft/util.smartptr.shared.general#1.sentence-3) |
|
Now we just have to decide whether follow should be local or not... I myself am unsure about that. I would say yes, as it affects the core language and a very important part of name lookup. Furthermore, it's also in [basic], which to me is kind of the clause 3 of ISO guidelines... |
|
Should this PR be closed then, or do we want the italics? We have like ten billion definitions that don't comply with the "don't make definitions italic" ISO rule, so is that ISO rule going to stop us from adding italics here? |
|
I think adding italics is the right move. |
|
Unlike shared pointers' empty, this is not a local definition to... to a paragraph? It applies to the program and translation unit. Paragraph in question:
|
|
I think this additional indexed definition will contribute to making C++ less ambiguous and easier to work with in future standardisation |
|
Can you please rebase? |
|
Yes, "follow" is a defined term here, and should be italics + indexed. |

Fixes #8142