Description

This seems like a common mistake. It consists on using code like this:

uN::from_str_radix(hex_slice, 16)

to decode a hexadecimal string into an integer, unintentionally (in most cases) allowing + as a valid prefix for hex sequences. I say "unintentional" because hex-strs typically represent arbitrary data, not numbers/numerals.

IDK if there's an existing lint-rule where this should be included, or if it warrants a new lint, that's why I've opened a blank issue

Version

Additional Labels

@rustbot label +C-enhancement