Canonicalize source script file path #156
Open
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
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.
Howdy howdy.
I noticed that when running my file with
rust-scriptdirectly rather than the shebang, that recompilation was occurring, as a whole new project was being created for a file I had used with a shebang earlier!It turns out that the path that
rust-scriptthrows together was different between runs to the same file, depending on how it was reached:Before:
After:
The canonicalization is technically a fallible operation, but I'd be very surprised if
cargodoesn't do the same internally. 🐈⬛I think this interacts positively with #121, as they also had issue with the same behavior I observed but under a different perspective.