Dan Rose

> The single file snapshot extension is meant for string or byte data Gotcha. That makes sense, though it wasn't obvious to me. Here are a few places that I...

After sleeping on it, I still think it's pretty unintuitive that "`SingleFileSnapshotExtension`" doesn't accept objects. I.e. I'd expect `SingleFileSnapshotExtension` to use the *same* `SnapshotSerializer` implementation but differ in implementation of...

> how do you convert something like a dict to bytes? It depends. 1. If the expectation here is to save the buffer byte-wise, then it *ought* to throw a...

> Just to be clear, this isn't going to work lol, I know. I reduced the repro example from something like `type Array = T[] & { push: (t: T)...

It seems there's an internal failure that happens before this crash. It's not my particular *definition* of the `Array` type that's a problem but using a type alias to define...

> It seems there's an internal failure that happens before this crash. It's not my particular _definition_ of the `Array` type that's a problem but using a type alias to...

> This is not supported. `Array` must be an interface. > > You're the only person trying to do this, please stop 😅 lol - gotcha. Wasn't sure if "this...

I think this might be a clearer example of part of this bug. Namely, while the function type *extends* both signatures, it can only *infer* the last return type. ```ts...

Related? #48837 / #55774 > In a homomorphic mapped type `{ [K in keyof T]: XXX }`, where `T` is constrained to an array or tuple type, `K` has an...

> The UX problem that we can recognize here is that all of those 3 display in the same way (`{ [k: string]: unknown; }`): > > ```ts > type...