hack: permit foo/bar/baz:version in toolchain names
#159
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
This was legal (accidentally?) in previous elan version, and let me smuggle Bazel target names into the `lean-toolchain` files. https://xkcd.com/1172 obvious applies here.
Member
|
I can't accept this if it just throws away parts of the regex match. But for local toolchains, even the version match doesn't make much sense. How about changing the code so that we simply accept |
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.
This was legal (accidentally?) in previous elan version, and let me smuggle Bazel labels into the
lean-toolchainfiles.Look, my setup works for me. Just add an option to reenable ...
Fixes #139