-
Notifications
You must be signed in to change notification settings - Fork 738
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
Should this be hosted under the isocpp organization on GitHub.com instead of Microsoft? #43
Comments
I wondered the same thing. I'd love to see some discussion around this. |
I think the idea is that isocpp sets the specifications and anyone can provide an implementation. This is Microsoft's effort but there is nothing preventing another project from implementing the specifications. The more the merrier perhaps? |
Yes, this is the reference implementation of the ideas behind GSL as envisioned in the Core Guidelines. We expected there will be more implementations. |
I think a reference specification would be benefitial for other implementors. From this implementation it is not clear which design decisions are mandatory and what details are allowed to vary. It is also confusing, as others have also noticed, that gsl overlaps and in places contradicts with the publicly available stl proposals (string_view, array_view). |
I agree. If we expect more implementations we need a specification, which currently is missing in the C++ Core Guidelines. |
This conversation is back to an issue on the isocpp repo: isocpp/CppCoreGuidelines#144 |
I think I understand why it is under Microsoft, but it feels weird. I think it would fit best directly beside https://github.com/isocpp/CppCoreGuidelines
Is this something that Microsoft would be okay transferring ownership over to the Standard C++ Foundation?
The text was updated successfully, but these errors were encountered: