Revert "Replace slashes with underscores in default crate names." #1335
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
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.
Reverts #1334
This commit inadvertently changed the location (directory) of the output created by rustc. Before this change, a rust_binary target named
bin/foowould create an executable namedfooin a new subdirectory namedbin. After this change, the same rust_binary target would create an executable namedbin_fooin the normal blaze output directory.The previous behavior is consistent with other bazel rule behavior (e.g. cc_binary), so rules_rust should keep that behavior. I'd like to roll this back, and create a new PR to handle slashes in a better way.