refactor: explicitly define host platform ordering #2890
Conversation
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
rickeylev
force-pushed
the
refactor.well.defined.host.platform.ordering
branch
from
e283fc0 to
b31a9a4
Compare
rickeylev
force-pushed
the
refactor.well.defined.host.platform.ordering
branch
from
b31a9a4 to
f88fc59
Compare
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.
It turns out the
unsorted-dict-itemsdisable in versions.bzl is load-bearing: theprecedence of what host-compatible runtime is selected depends on the order of keys.
Hence, the keys are carefully defined such that freethreaded and musl come after the
regular runtimes.
Make this subtle and implicit behavior explicit by having an ordering function that
sorts keys in the order we want.
DO NOT MERGE: awaiting #2889
Work towards #2081