std-freestanding-alloc-kal 0.1.1: it declares what it is built against - #268
Merged
Conversation
⚠️ `openkal = "0.5.1"' bounds the package below 0.6.0 --- a caret on a 0.x version stops at the next minor --- so it had been resolving 0.5.x while the specification released 0.6, 0.7 and 0.8. Nothing was broken by that and nothing would have reported it: clause 8 forbids the specification from altering a declaration it has published, so `kal_alloc' and `kal_free' mean in 0.8.0 exactly what they meant in 0.5.1. That is the reason to move rather than a reason not to. A package declaring a version it does not test against records what it was written against and stops recording what it works with.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
openkal = "0.5.1"bounds the package below 0.6.0 — a caret on a0.xversion stops at the next minor — so it had been resolving 0.5.x while the specification released 0.6, 0.7 and 0.8.kal_allocandkal_freemean in 0.8.0 exactly what they meant in 0.5.1. That is the reason to move rather than a reason not to: a package declaring a version it does not test against records what it was written against and stops recording what it works with.Its own
mainrun is green on the new pin, and both mirrors were fetched back and compared before the hash was written here.