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

Stable names in 20.11 are too long #794

Closed
jwakely opened this issue Jul 5, 2016 · 8 comments
Closed

Stable names in 20.11 are too long #794

jwakely opened this issue Jul 5, 2016 · 8 comments

Comments

@jwakely
Copy link
Member

jwakely commented Jul 5, 2016

[memory.polymorphic.allocator.class]
[memory.resource.monotonic.buffer.ctor]

Surely we can abbreviate these.

@jwakely jwakely changed the title Stable names in 20.11.6 are too long Stable names in 20.11 are too long Jul 5, 2016
@tkoeppe
Copy link
Contributor

tkoeppe commented Jul 5, 2016

Best to fix that before we commit to the stable names!

@tkoeppe
Copy link
Contributor

tkoeppe commented Jul 5, 2016

[mem.poly.alloc.class]
[mem.res.mono.buf.ctor]

@AlisdairM
Copy link
Contributor

looking at Annex F for long names, these are far from the only culprits. Seems to be an issue with many stable names from the TS. Compare: fun.wrap.badcall vs. optional.bad_optional_access - we have forgotten how to abbreviate.

Also, underscores seem to make the names look much longer in Annex F - see the Boyer Moore searchers.

@jwakely
Copy link
Member Author

jwakely commented Jul 6, 2016

Yes, underscores are sometimes replaced with dots instead, e.g. unique.ptr, which looks much better.

[optional.bad.access] or [optional.badaccess] seem better than [optional.bad_optional_access].

I'm also not sure we really need to keep the word "object" in [optional.object.] ... I think it was there to reserve place for [optional.ref.] but we don't have optional<T&> and even if we did we could still use [optional.ref.*] once we add it.

@cpplearner
Copy link
Contributor

The longest one seems to be [func.searchers.boyer_moore_horspool.creation] in 20.14.13.3.1, and it formats badly in the new xrefs.

@tkoeppe
Copy link
Contributor

tkoeppe commented Nov 12, 2016

@jwakely, @AlisdairM, @zygoloid: We should fix this before we ship the IS!

@jwakely
Copy link
Member Author

jwakely commented Nov 12, 2016

GB 52 covers this.

@jensmaurer
Copy link
Member

Those long names are also the cause for overfull/underfull hbox complaints from LaTeX; see #693.

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