Stdlib: rename binary operations to match JavaScript terms

[cometkim]

• Left Shift
• Right Shift
• Unsigned Right Shift
• Bitwise AND

So on

[cknitt]

👍 for cleaning up the naming/adapt it to JS terms.

Some questions:

• Why not keep the Bitwise submodule? Modules/applications that do a lot of bitwise operations might want to open just that submodule.
• Wouldn't shiftLeft/shiftRight/shiftRightUnsigned be better naming than leftShift/rightShift/unsignedRightShift (e.g., for grouping these functions together in autocomplete)?
• Do we need deprecations for the old functions (for those migrating from Core)?

[cometkim]

I simply didn't think it was necessary to hide the bitwise operations, so I adjusted them to be consistent across multiple modules.

Wouldn't shiftLeft/shiftRight/shiftRightUnsigned be better naming than leftShift/rightShift/unsignedRightShift (e.g., for grouping these functions together in autocomplete)?

Yeah it could be. If it becomes a common convention on the Stdlib surface, it's worth following.

[cknitt]

@zth What are your thoughts regarding function naming / the Bitwise submodule?

[cknitt]

Yeah it could be. If it becomes a common convention on the Stdlib surface, it's worth following.

We already have reduce and reduceRight (not rightReduce), for example.

[cknitt]

Thanks a lot! 👍

[cknitt]

Ah, sorry, need to ask about a CHANGELOG entry again.

[cknitt]

Merging as is, will add the CHANGELOG entry while preparing the release.