Alec Helmturner

Also, if we implement a single shared stream connection, we would just keep it open for _all requests_. Batches, chunks, single results - they all get sent down the wire...

> The issue I'm having with this one is that it kind of implies (unless you have an alternative idea) that the last streamed data (the `return`) includes "everything". Like...

> - you can think "SSE" and assume "a list of events" > - or you can think "stream" and assume "a single block of data returned over time" Hmm,...

I think @iamnafets sums up what I've been very longwinded in saying. It's also worth noting that, if you want to avoid resending the reconstructed final result again over the...

@H4ad We've got an [open discussion on discord](https://discord.com/channels/867764511159091230/1156727678267822120/1168660426721083542) about serverless runtimes and new, http-based streaming features. Care to weigh in?

@nicolassanmar I believe if you use edge routes it 'just works' edit: If, that is, you're referring to the tRPC streaming features, not those in NextJS (which are new to...

I'm experimenting with a utility class that generates convenience methods for variations on a schema, and I've found the easiest path is to define defaults on the schema and recursively...

> @maxArturo that is actually what I ended up doing end I found that it doesn't work because the dist files are (rightfully) not in the repo. But you can...

What if this were implemented > ## RFC for datetime methods > The hard problem here is naming the methods such that the validation behavior is clear to everyone. I'm...

Oh, this is good! ```ts const test = [1, 2, 3] as const; const test2 = [...test, 4] as const; const test3 = [0, 2, 3] as const; let val...