We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
How do we want to employ semantic versioning for this library?
Thrust for instance updates the release version by hand by setting new values in thrust/version.h.
This is required if we opt for versioned inline namespaces to solve #189.
The text was updated successfully, but these errors were encountered:
cuCo doesn't have a release yet thus I'm not sure how to incorporate the versioned inline namespace in our case. e.g. how to name the version.
Sorry, something went wrong.
Yeah, that's true. Maybe we could push a development tag 0.1.0 to dev and use that as an intermediate?
0.1.0
dev
Inline namespaces won't solve #189 in the short term because we aren't going to bump the version with every PR.
The best short term solution for #189 is the custom namespace prefix.
Ok, then we can put this issue in the backlog for now.
No branches or pull requests
How do we want to employ semantic versioning for this library?
Thrust for instance updates the release version by hand by setting new values in thrust/version.h.
This is required if we opt for versioned inline namespaces to solve #189.
The text was updated successfully, but these errors were encountered: