Bitwise operations on BigDecimal

[littledan]

I can't figure out what sense bitwise operations like |, & and ^ would make on BigDecimal. My intuition is that we should just throw TypeErrors if they are used. Any concerns with this plan?

[MaxGraey]

What about use 1.5m | 0n or 1.5m >> 0n for converting to BigInt? Not sure is it good idea but some JavaScript users could expect this behaviour. 1.5m | 0 and 1.5m >>> 0 should of course restrict.

[littledan]

I'm wondering, what would the downside be of requiring that people explicitly cast to BigInt in those cases?

[Rudxain]

@littledan We would expect code that looks like this: BigInt(BigDecimal.trunc(x)) & 0xffn (where x is a BigDecimal), which looks very verbose even if
this proposal got to Stage 3, which would instead look like BigInt(Math.trunc(x)) & 0xffn, which is shorter, but still has the same number of tokens. This was just an example, the expression can be simplified to BigDecimal.trunc(x % 256m), but the issue gets worse with operators such as XOR ^ which would require loops to emulate mathematically look like this BigInt(BigDecimal.trunc(x)) ^ y) , although I don't know of any use case for XORing a BigDecimal as if it were an int