any vs unknown on DTFunction#bindundefined->0 coercion under strictNullChecks for bitwise opsfiles arraytypeof (expression) operandsany vs unknown on DTunknown would have acted as any under non-strictmixed type that is unknown in strict and any otherwisestrictUnknown probably actually wants strictAnystrictAny and try to work through its problems againany in output positionsunknown in input positions is OKFunction#bindfiles arrayIt's not up to randos on DT to decide your strictness policy
As one of those randos, this is a continuous concern of mine! It would be good if DT had a fairly complete style guide about things along these lines, but that's a different issue (specifically https://github.com/DefinitelyTyped/DefinitelyTyped/issues/2001 which lead to the now quite out of date and incomplete http://definitelytyped.org/guides/best-practices.html)
Most helpful comment
As one of those randos, this is a continuous concern of mine! It would be good if DT had a fairly complete style guide about things along these lines, but that's a different issue (specifically https://github.com/DefinitelyTyped/DefinitelyTyped/issues/2001 which lead to the now quite out of date and incomplete http://definitelytyped.org/guides/best-practices.html)