added a comment - - edited
This does way too much, and thus makes it hard to talk about.
Moving unchecked coercions into unchecked ns is ok, and would make a fine and acceptably-sized patch.
unchecked double makes no sense to me at all - no double ops are checked
There seems to be general confusion about unchecked vs primitive-taking. Only a small subset of ops have the overflow checking that is turned off by 'unchecked'
There's no sense in which the interacts with *unchecked-math*, nor with the latest numerics approach (primitive semantics by default)
There's a ton of duplication with things already in Numbers that handle primitive overloads. esp. in combination with different primitives and objects.
The things we need for bit ops are lost in the noise.
What I want for bit ops is the same thing we currently (in latest) have for other ops - primitive semantics by default, no conditionals, direct mapping to JVM primitive ops.
And separate tickets and patches for each step, please. This is simply too much to consider.