-
Notifications
You must be signed in to change notification settings - Fork 198
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
[#455] If constructor arguments fail to resolve, propagate failure #456
Conversation
ec7a143
to
b436083
Compare
Latest push corrects the issue number in commit comment, no code change from previous. |
Thanks for the PR - for now I make the same comment as #448 (comment) |
b436083
to
72cced5
Compare
Rebased on current main. |
… failure This change prevents invalid partial specialisations from being chosen when instantiating a template in cases where the expression for the type/value of a template parameter involves a constructor call.
72cced5
to
4ec1115
Compare
This change looks good and functions as advertised. |
@jonahgraham Could this be merged? |
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.
At recent CDT calls we discussed how to handle reviews where there is insufficient expertise to review amongst existing committers and decided to accept such changes that look reasonable and appear sufficiently tested.
Thank you @davmac314 for this improvement! |
This change prevents invalid partial specialisations from being chosen when
instantiating a template in cases where the expression for the type/value of a template parameter involves a constructor call.
A test is included.