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.

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

A13-3-1: reconsider precision and feasibility of rule exception #524

Open
knewbury01 opened this issue Feb 7, 2024 · 0 comments
Open

A13-3-1: reconsider precision and feasibility of rule exception #524

knewbury01 opened this issue Feb 7, 2024 · 0 comments

Comments

@knewbury01
Copy link
Contributor

knewbury01 commented Feb 7, 2024

the standard lists an exception where some explicit constructors may be constrained and therefore not actually overload implicit copy/move ctors.

the current implementation does not cover this,

further consideration is required to determine if the exception is possible and also valuable

consider the following :
not c.getTemplateArgument(_).toString().matches("%enable_if%") or maybe not c.getTemplateArgumentKind(_).toString().matches("%enable_if%")
but this wont work for functions where the types in the argument actually resolve if the function is called

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant