version: 0.5.0 -> 0.6.0 #81
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
why not 0.5.1? there have been no breaking changes afaict? |
|
Conversation has been light, but hopefully we can have #78 merge before the next release. It would require a breaking change of choice of algorithm. There hadn't really been any feature activity on this repo until I opened that PR. I would assume that the 0.6 vs 0.5.1 choice is because of the algorithm choice change. |
|
I would appreciate that we could have a 0.5.1 with the |
|
Seems like we could do both allocator_api 0.5.1 and allocator choice 0.6. I don’t see any reason why we need to wait for either besides the natural flow of open source PR review. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.