-
Notifications
You must be signed in to change notification settings - Fork 180
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
fix debug print of pointer types #608
Conversation
While we are at it, is there a specific reason for application types to be printed as ugly as they are now, or I can go ahead and change them to be rendered "properly"? |
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 think we should add a impl Debug for Mutability
instead, to avoid doing this for each place where it can occur.
While we are at it, is there a specific reason for application types to be printed as ugly as they are now, or I can go ahead and change them to be rendered "properly"?
I'm assuming it's there because implementing Debug directly doesn't work, but if we don't need it then feel free to simplify it.
I am not sure how to do that, it renders to different things when in different places, i.e. By ugly I didn't mean the implementation, I meant that printed types are in |
Ah right, did not notice that. |
So, yeah, debug printing of |
@Areredify feel free to followup with this, if you want. Or just file an issue for someone else to followup. In the meantime: @bors r=jackh726,detrumi |
📌 Commit 3434f66 has been approved by |
☀️ Test successful - checks-actions |
Fixes confusing debug print of pointer types, previously
&'a T
it was printed asNot<!0_0, T>
and*const T
was printed asNot<T>
, which was not ideal.