Simple Comparison of Generics not allowed?

TypeScript Version: 3.8

Search Terms:
generic comparison
compare generic strings

Code

function test<A, B>(one: A, two: B): A {
  if (one === two) {
    throw new Error('no');
  }
  return one;
}

const obj = {};

test(obj, obj);

Expected behavior:

While the generics are generally indicating that one and two are independent values, they can still potentially be the same underlying value so they should be able to at least be checked for equality without casting them first, especially since there is no error produced when calling the function with identical values in the first place.

At the very least the error message should be more specific since the assumption it is providing is not correct in since the condition returns true :-P

( This is clearly a simplified version of where I ran into this since there'd be no reason to use generics in this specific case :-) )

Actual behavior:

Shown in example

Playground Link: Playground

Start with the TypeScript 3.8 Playground link and the generic test<A, B> reproduction in the issue. Investigate the type-checker diagnostic for comparing one === two when A and B are independent type parameters. Done means the comparison behavior or its diagnostic matches the stated expectation, with coverage for the shown example.