fix: use lib.name instead of package.name if possible - #98
Merged
Conversation
GregoryConrad
approved these changes
Aug 18, 2026
GregoryConrad
left a comment
Owner
There was a problem hiding this comment.
Thanks for the contribution!
Owner
|
If I don’t make a new release this evening, please bug me here for a reminder 😅 |
Contributor
Author
Got it, thx for merging |
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.
when rust compiles the library, and lib.name is defined, the pattern lib{lib.name}.d is used instead of lib{package.name}.d, So this PR covers this.
Previous to this PR, this wouldn't compile
Solves #97