-
Notifications
You must be signed in to change notification settings - Fork 735
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
Future of the ms-gsl. Versions, Releases, Supported Compilers, New and Removed features #348
Comments
@MikeGitb thanks for the question, and especially, thanks for the kind words. I'll address your questions in order, and refer by their numbers, to make what will be a long answer hopefully a little easier to follow.
I hope those answers are useful. If not, or you need more detail to better answer the question, just let me know. Note that my talk at CppCon 2016 also covered some of this material and can be viewed at: https://www.youtube.com/watch?v=_GhNnCuaEjo. |
So... about release labels... Will we be getting any of those anytime soon? I've noticed that the version of the GSL that comes with the Nuget package for VS 2015 is at least a little bit behind the trunk here on github (it still has I am interested in pulling down a newer version of the GSL than what is in the Nuget package. I would like to have a solid version number to track with, so we can be conscious of exactly which version of the GSL we are using in comparison to what is available. Right now, with no releases or tags of any kind, that seems rather hard to do. |
Now that the features of the gsl seem to have somewhat stabilized, I'm wondering what the plans for the future development of this library are (I'm mainly talking about Microsoft's gsl in particular - not so much about the gsl-specification).
That encompasses quite a few different but related questions:
Now I'm not expecting you to have a answer to all of this (and certainly not a time table or fleshed out policy) but it would be nice to know, how ms is currently envisioning this library's future development.
Most of all: Thank you very much for providing and maintaining this little jewel.
The text was updated successfully, but these errors were encountered: