scryptenc_print_error.c: add a "default" for safety#391
Merged
Conversation
Member
Author
|
We should never need this, but there's no harm in adding it. |
Member
Author
|
FWIW, this was inspired by tarsnap's https://github.com/Tarsnap/tarsnap/blob/master/lib/keyfile/keyfile.c#L199 |
gperciva
force-pushed
the
print-error-default
branch
2 times, most recently
from
f493593 to
35fd6b0
Compare
We should never reach that "default", but that doesn't mean that it'll never happen.
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
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.
No description provided.