RangeBounds::is_empty has a nonsensical implementation (original) (raw)

Essentially per rust-lang/libs-team#277 (comment)

pingback rust-lang/libs-team#539 and #137300

"The range is non-empty, but there's no values that fulfill it in the type" is a goofy statement.

Filing this issue on behalf of @judnich seeing as @quaternic mentioned he didn't file an issue after being asked to participate in our bureaucratic nonsense. I agree with the objection: the values of interest are the values in the type, not some hypothetical value line which includes all possible inbetween gradients like the reals. That's not even a coherent notion for types which don't themselves represent a subset of some notional superset. To wit: not everything is an integer.