Does the using-declaration to add it to std need the // freestanding comment too?

Does the using-declaration to add it to std need the // freestanding comment too?

This relates to #5724 (comment). The using-declaration is a declaration, which can be a freestanding entity, but the literal instructions was to mark entities and not declarations and macros definitions.

But https://cplusplus.github.io/LWG/issue3753 changes that.

It fixes the definition But does not

clarify whether the paper's instructions to the editor that mention "every entity" actually meant "all declarations and macro definitions".

The same #5396 which moved get, also moved memory_order variables which are not marked freestanding. That's consistent with the instructions to mark entities, because a variable is not an entity, but inconsistent with the fact that headers marked "all freestanding" have their variables be freestanding because they are declarations. The paper even instructed to explicitly mark some variables as freestanding.

The intention of the paper is pretty obvious, even if the wording was imprecise. Let's not insist on inferior outcomes because of that imprecision. Expect NB comments to ensure everything is freestanding.

My question is not "did the precise wording in P1642R11 say to mark this using-declaration freestanding", it's whether it needs to be or not. I think it does need to be.

Does the using-declaration to add it to std need the // freestanding comment too?

Then yes is the answer I expect it to be.

"An entity is a value, object, reference, structured binding, function, enumerator, type, class member, bit-field,
template, template specialization, namespace, or pack."

Those variables are objects, no?

AFAIK, the variables designate objects.

6# A variable is introduced by the declaration of a reference other than a non-static data member or of an object.
The variable's name, if any, denotes the reference or object.

@jwakely , feel free to mark the using-declarations as freestanding, too.

Done.