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

decltype isn't resolved when followed by & #286

Closed
niklasnolte opened this issue Jan 14, 2020 · 2 comments
Closed

decltype isn't resolved when followed by & #286

niklasnolte opened this issue Jan 14, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@niklasnolte
Copy link

https://cppinsights.io/s/6f62be64 vs https://cppinsights.io/s/8b0c93a7

In the case where the decltype(v) is followed by &, the type does not get resolved.
Is this wanted behaviour?
@andreasfertig andreasfertig added the bug Something isn't working label Jan 15, 2020
@andreasfertig
Copy link
Owner

Hello @niklasnolte,

thank you for spotting & reporting this. I consider it a bug and not the wanted behaviour. A fix is on its way.

Andreas

andreasfertig added a commit that referenced this issue Jan 15, 2020
@andreasfertig
Fixed #286: Desugar decltype(x) even when it is an LValueReference.
9bcbc4e 
This case was missed before and should be expanded as well. A few other
places turned up which profit from that change.
@niklasnolte
Copy link
Author

thanks for the quick fix @andreasfertig !

andreasfertig added a commit that referenced this issue Jan 15, 2020
@andreasfertig
Merge pull request #287 from andreasfertig/fixIssue286
626830d 
Fixed #286: Desugar decltype(x) even when it is an LValueReference.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@niklasnolte @andreasfertig