Mateusz Burzyński

I’d appreciate any kind of repros - they could even be not-so-minimal 😉

This changes the behavior even in 5.5: ```diff interface Observable { pipe(op: OperatorFunction): Observable; } type OperatorFunction = (source: Observable) => Observable; -declare function tap(next: (value: T) => void): OperatorFunction;...

Sort of a duplicate of https://github.com/microsoft/TypeScript/issues/48363 but with object types. It repros the same way when I wrap function arguments from that issue in objects: [TS playground](https://www.typescriptlang.org/play/?ts=5.7.0-dev.20240824#code/PTAECEHsA8B4BUB8oAuBPADgU1ASwM54B2AbgIYBOuZRKxo8AsAFAvrYQwLIC8oA3i1CgA5lhQAuUAAoAlKB7J4AbiGh84qdPIAbAK5Yp8eYtAlIuACarmAXxstLWAMY7KOAGZ6izlLkhEoABGXEjaZPqGDLJSUHBIDszOAfh0QUQAjArBMNL8oBgUkBhSAAygtrLKoCCccPmFxVJEegC2QVgUFYgsyUSpwUQATLFcDUUloC3tnd3ZIdB5BRNlFVU1YADyANYsvSlpQVl8C0uNkx4RGmvVtXGw4005kDpYNN37-YcjdQ-LTyEXm9ArZeDlFo8LlccJVbmAAKIUIoUAA04L+5yklx011BU0gdDI+HwuBERDIQVeqEgv0hUkBr3eoJYQA).

Well, `boolean` is a union of `true | false` so it makes sense that unions are affected 😉 It's just that `boolean` is expected to behave more like a primitive...

@RyanCavanaugh I think it's the one I posted above, the one with `"foo" | "bar"`.

It depends on how TypeScript breaks down your union. The inference targets are not at the same level so TypeScript can't discriminate this by how the target is contained in...

I don't have the energy right now to minimize this Ramda madness further. This is what I got so far: Repro ```ts declare type Cast = A1 extends A2 ?...

We already have a Ramda-based repro, see even the rolled up one [here](https://github.com/microsoft/TypeScript/issues/60278#issuecomment-2423332955). The problem is that their types are very complex - for somebody to investigate this issue it...

The problem here is that getters are resolved eagerly even though they might have a context-sensitive dependency on `this`. It's not something that methods suffer from even though they *might*...

Tbf, one of the first ones I linked to should be closed in the favor of the other. They look like duplicates to me - but it’s up to @RyanCavanaugh...