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
Cleanup make-unsigned-like #3311
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok with this change, although I'd like to point out that making "make-unsigned-like-t" an alias template was not specifically approved by the editorial meeting.
It might actually be a good idea to gravitate towards alias template syntax for exposition-only type metafunctions.
@CaseyCarter , this needs a rebase. |
So rebased. |
Rebased again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks, Casey.
I'm strongly in favour of using angle brackets for the type transformation metafunction.
Uh, it seems the other check-in created a conflict here, yet again. @CaseyCarter , please rebase. |
...instead of an exposition-only macro. In other words, it's used as `make-unsigned-like-t<meow>` instead of `make-unsigned-like-t(meow)`.
Rebased harder. |
...per the direction of #3300. This PR consists of three commits:
make-unsigned-like
toto-unsigned-like
make-unsigned-like-t
from an exposition-only macro (invoked with parentheses) into an exposition-only alias template ("invoked" with angle brackets)x
of typeX
,to-unsigned-like(x)
is..." to "For an expressionx
".I believe the change from
()
to<>
in the second commit makes the occurrences ofmake-unsigned-like-t
read better in the text - as well as increasing the intentional similarity withmake_unsigned_t<meow>
- but this change doesn't appear to have been discussed in the editorial meeting.