The type of bitwise operations on 'any' operands should be 'number | bigint'

[fasttime]

Bug Report

🔎 Search Terms

• bigint
• bitwise

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about bigint.

⏯ Playground Link

Workbench Repro

💻 Code

//@target: ES2020
const v1 = 1n as any;
const v2 = 2n as never;
const v3 = v1 | v2; // v3 should be typed (number | bigint), but is number

🙁 Actual behavior

The result of the bitwise operations &, |, ^ and ~ is assumed to be a number when all the operands have unspecified type, like any or never.

🙂 Expected behavior

The result of bitwise operations with unspecified type operands should be number | bigint.

[MartinJohns]

The result of bitwise operations with unspecified type operands should be number | bigint.

That wouldn't make your example 2 valid. You could still call bitwiseAnd with a bigint and a number, resulting in an error. Same issue as #12410.

[fasttime]

@MartinJohns You must be right. I fixed my sample code, thanks!

[MartinJohns]

I fixed my sample code

You really didn't, because you can't. There's no way to currently type this in a safe way, as mentioned in #12410 already. You would need #27808 for this.

typeof at the type level does not refer to the runtime type of variables. In your updated example 2 typeof a is just a synonym for I. A very common misconception of I extends number | bigint is that I can only be number or bigint, but it can be number | bigint as well.

const a1 = 123; // number
const a2 = 456n; // bigint
bitwiseAnd(a1, a2); // calling with number and bigint.

// Or alternatively
bitwiseAnd<number | bigint>(123, 456n);

[fasttime]

In that case, I'll leave that part out of my example. Why am I using TypeScript anyway?

[MartinJohns]

Related: #41741 (possibly a duplicate)

[fasttime]

Clearly TypeScript thinks that certain operators can produce nothing but a number, which used to be true (i.e. -value), but no longer holds in times of bigint.

[MartinJohns]

The issue I last linked was for TypeScript 4.2.0, bigint already exists for quite a while longer. The decision made in that issue does not refer to a state that "used to be true", but to the current version.

From the TypeScript Design Goals:

Non-goals
3. Apply a sound or "provably correct" type system. Instead, strike a balance between correctness and productivity.

I would guess that in the majority of cases number is an appropiate type, and having it result in number | bigint would just cause additional headache. Less correctness, more productivity. And IMO when you use bitwise operands on any or never you already left the world of type-safety anyway.

[fasttime]

Well, I wasn't talking about the state of the dev version of TypeScript, but the current version of ECMAScript, or ES2020, where bigints are introduced as part of the language (JavaScript, not TypeScript). Certain expressions that could previously only produce number values now produce bigint values.

It is well possible that the current TypeScript behavior with respect to the typing of such expressions strives to enhance productivity at the expenses of correctness. I would say though that legacy compatibility also needs some consideration here, as changing the current behavior would break existing code.

[andrewbranch]

The result of the bitwise operations &, |, ^ and ~ is assumed to be a number when all the operands have unspecified type, like any, never, number | bigint, etc.

Importantly, this statement is false insofar as it includes number | bigint. number | bigint is not a valid operand for any binary bitwise operator, and when applied to a unary bitwise operator (~), the result is correctly typed number | bigint.

It seems like #41741 intended to suggest what you are suggesting, but incorrectly asserted that an expression like -x | y where x: any and y: bigint should not be an error. We now disallow this because we say -x is a number. If we were to call it a number | bigint, the expression would still be an error because it still might be a number, which would throw.

It’s possible that the incorrect formulation of that issue caused it to be dismissed without really considering the suggestion here. I tend to agree with @MartinJohns that this would be a huge pain, and the existing workarounds of “avoid direct unchecked manipulation of any” or “annotate variables as number | bigint when they are inferred as number but you know they might be bigint” are pretty good workarounds. It is possibly the sort of thing we’d add a pedantic flag for, but only after a significant showing of public support for it.

[andrewbranch]

I would also say that maybe you shouldn’t be allowed to use never in any kind of bitwise/arithmetic operation, but that seems to be its own weird problem

declare let a: never;
const x = a + a; // number, no error
const y = "a" + a; // no error

[fasttime]

@andrewbranch you are correct, I removed the mention of number | bigint from the list of operand types that cause the issue to show up. Not sure what other types are affected besides any and never.