quaternic

> ```rust > fn overlaps(&self, other: &O) -> bool > where > T: PartialOrd, > E: ?Sized + PartialOrd, > O: RangeBounds, > ``` > Functions like `overlaps` or `intersect`...

First off, I do agree withs the points that having to write `std::f32::consts::PI` is a pain, and `f32::PI` just working would be a very reasonable expectation. However, the mathematical constants...

> And if typeof is ever added it will be possible to do > ```rust > for x in data { > if x.abs() // ... > } > }...

> This is neat, but all general-purpose programming languages that I know of just have floating-point constants for π, etc., and they seem to get along fine without all this...

>And there is a caveat: while IEEE specifies that float operations can never output a signaling NaN, Rust float operations *can* produce signaling NaNs, *but only if* an input is...

This similar issue in `glfw` has some informative discussion: https://github.com/glfw/glfw/issues/1630 I've realized I can easily work around it by changing the keymods in my event handlers, but it's not a...