Prevent compiler warning without panicking #1084
Merged
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.
My attempt at resolving #1068.
The source of the panic seems to be an assertion that was added purely to remove a compiler warning, so I turned it into a warning because I don't think an empty version field should prevent updating to a latest PR.
TODO: If people decide this is an acceptable solution, I'll improve the warning message with potential causes.
One cause is when an installed channel has an empty version field due to not being able to get the version number from a non-codesigned executable on macOS #1068 (comment). It could also be that a particular PR was merged #1068 (comment).