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

GSL Expect() and Ensure() and the CppCoreGuidelines naming convention #993

Closed
franzhollerer opened this issue Jul 22, 2017 · 3 comments
Closed

Comments

@franzhollerer
Copy link
Contributor

I would prefer if Expect() and Ensure() used in I.6, I.7 follow the CppCoreGuidelines naming convention.

@MikeGitb
Copy link

Me too, but the gsl maintainer have repeatedly refused to make changes to Expects and Ensures in the past
microsoft/GSL#35
microsoft/GSL#75
#227

@neilmacintosh
Copy link
Contributor

@franzhollerer If you look at the issues @MikeGitb has referenced, you can see the reasoning for the existing naming convention approach. The fact that these calls happen to be macros is an unfortunate and (hopefully) temporary implementation detail. We would not want to reflect that state of affairs in their names, especially when they are such critical pieces of the approach taken in the Guidelines.

@franzhollerer
Copy link
Contributor Author

Thanks @MikeGitb and @neilmacintosh for pointing me to the related issues.

I merely noticed that their naming neither follow the naming convention for macros, nor for functions, but start with an upper case which would indicate a type. Anyway, that's a negligible flaw.

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

3 participants