Skip to content

make-unsigned-like and make-unsigned-like-t are too similar #3300

Closed
@CaseyCarter

Description

@CaseyCarter

[ranges.syn]/1 defines an exposition only function make-unsigned-like and an exposition-only metafunction make-unsigned-like-t. These two names are hard to distinguish, doubly so with an argument list:

make-unsigned-like(meow) vs. make-unsigned-like-t(woof).

It would help somewhat if make-unsigned-like-t were treated as an exposition-only alias template:

make-unsigned-like(meow) vs. make-unsigned-like-t<woof>

but ideally the names themselves should be more distinct as well. @jwakely suggests renaming make-unsigned-like to as-unsigned-like or to-unsigned-like, which preserves the intended similarity between make-unsigned-like-t and make_unsigned_t.

(As discussed in #3299 (comment)).

Activity

added
decision-requiredA decision of the editorial group (or the Project Editor) is required.
on Oct 16, 2019
jensmaurer

jensmaurer commented on Oct 21, 2019

@jensmaurer
Member

Editorial meeting: When we have exposition-only foo and foo-t, their relationship should be the same as any other bar and bar_t. That's not the case here. Rename "make-unsigned-like" to "to-unsigned-like".

removed
decision-requiredA decision of the editorial group (or the Project Editor) is required.
on Oct 21, 2019
added a commit that references this issue on Oct 21, 2019
4430b41
added a commit that references this issue on Nov 25, 2019
d534964
added 2 commits that reference this issue on Jan 24, 2020
a06d0b2
4367e71
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @CaseyCarter@jensmaurer

      Issue actions

        make-unsigned-like and make-unsigned-like-t are too similar · Issue #3300 · cplusplus/draft