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.

Sign up for GitHub

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

Jump to bottom

Need an equivalent of [fs.req.namespace] for chrono LWG 2818 #3510

Open
zygoloid opened this issue Nov 23, 2019 · 5 comments
Open

Need an equivalent of [fs.req.namespace] for chrono LWG 2818 #3510

zygoloid opened this issue Nov 23, 2019 · 5 comments
Labels
lwg Issue must be reviewed by LWG.

Comments

@zygoloid
Copy link
Member

zygoloid commented Nov 23, 2019 •
edited

Much of the wording in [time] names members of std::chrono by unqualified name, in violation of [contents]p3. But there is also some explicit chrono:: qualification (eg: [tab:time.clock], [time.clock.utc.overview], [time.clock.conv], ...) even when describing entities in the std::chrono namespace.

We should decide if we want an equivalent of [fs.req.namespace], and either add it (and remove the then-redundant chrono:: qualifications throughout), or add all the missing chrono:: qualifications.
@zygoloid zygoloid mentioned this issue Nov 23, 2019
Merged
@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Dec 8, 2019
@jensmaurer jensmaurer added this to the C++23 milestone Feb 10, 2020
@jensmaurer
Copy link
Member

jensmaurer commented Feb 10, 2020 •
edited

Editorial meeting: Names in the standard library are looked up using unqualified lookup from their declarative region. Integrate into "no ADL by default" phrasing in the library front matter.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Feb 10, 2020
@jensmaurer jensmaurer removed this from the C++23 milestone Feb 10, 2020
@mclow
Copy link
Contributor

mclow commented Feb 13, 2020

This is related to lwg2818.

@jensmaurer jensmaurer changed the title need an equivalent of [fs.req.namespace] for chrono Need an equivalent of [fs.req.namespace] for chrono LWG 2818 Mar 10, 2020
@jensmaurer
Copy link
Member

After LWG 2818 has landed, it might need some tweaks and we should editorially remove the remaining (now useless) boilerplate.

@jensmaurer jensmaurer added the lwg Issue must be reviewed by LWG. label Mar 10, 2020
@JohelEGP
Copy link
Contributor

Not exactly the right place, but http://wg21.link/LWG2818's "further" seems problematic when x is used "before" it appears declared in the document. Also F is redundant.

@frederick-vs-ja
Copy link
Contributor

frederick-vs-ja commented Oct 11, 2023 •
edited

LWG2818 has landed.

In addition to chrono::, current occurences of std:: in [time.zone.zonedtraits] and [time.format] (except for those in the synopses) seem to be redundant.

It's still unclear to me whether qualification (or absense of qualification) of identifiers in [time.clock.req] is correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lwg Issue must be reviewed by LWG.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mclow @zygoloid @JohelEGP @frederick-vs-ja @jensmaurer