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

Should this be hosted under the isocpp organization on GitHub.com instead of Microsoft? #43

Closed
michaelbprice opened this issue Sep 24, 2015 · 6 comments
Assignees
Labels

Comments

@michaelbprice
Copy link

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?

@kylog
Copy link

kylog commented Sep 24, 2015

I wondered the same thing. I'd love to see some discussion around this.

@galik
Copy link
Contributor

galik commented Sep 24, 2015

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?

@gdr-at-ms
Copy link
Member

Yes, this is the reference implementation of the ideas behind GSL as envisioned in the Core Guidelines. We expected there will be more implementations.
We are considering the suggestion of moving to isocpp.org with great interest and will give you updates.

@tamaskenez
Copy link
Contributor

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).

@viboes
Copy link

viboes commented Sep 25, 2015

I agree. If we expect more implementations we need a specification, which currently is missing in the C++ Core Guidelines.

@AndrewPardoe
Copy link
Contributor

This conversation is back to an issue on the isocpp repo: isocpp/CppCoreGuidelines#144

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

No branches or pull requests

8 participants