Make the errors mapping table entries less cryptic #11
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.
I've spent hours debugging the following panic message thrown when a value larger than the 8 bits defined in the timer and error vector constants (I was trying to put
0x320
in the timer vector field and0x280
in the error vector field per what's specified on osdev.org) is plugged into the builder functions:This message is coming from the
bit
crate, which performs anassert_eq!
check to ensure that the bits are of the same length. Yet, it does absolutely nothing to inform the developer of what is being done wrong. So, I'm submitting this pull request to save other people the trouble by printing a more legible error message.