Callionica

I have isolated an example of hitting this error when trying to provide types for a function that deals with async iterables. Error is only hit when the function implementation...

Don't know if reproducible but the latest occurrence worked like this: I tapped a post from a thread to see the thread at that point The thread was slow to...

FYI due to this bug, I've switched from using the iOS app to using the mastodon.social website on iOS.

I get the message "Fatal JavaScript out of memory: Ineffective mark-compacts near heap limit" in a previously working and untouched app. I assume that's the same bug?

Does 1.33.2 do anything to fix/workaround this? Is my app unusual for hitting this? I'd kind of expect a lot of noise and activity around a regression like this, but...

I've implemented a version of a function call type-checking algorithm that involves spread and there weren't any particular challenges. It's a demo/POC - not a changelist - using a mini-parser...

These are interesting test cases, but I don't have a PR, it's a demo and it doesn't involve generics or inference. TS' spread support is currently a bit limited in...

Non-generic test case that fails in Typescript 4.7.4: ``` declare function fn(p0: number, p1: string, ...rest: string[]) : void; declare const a0 : number; declare const a1 : string[]; fn(a0,...

Another unexpected compile error: ``` declare function fn(p0: number, p1: string, p2?: number) : void; declare const a0 : number; declare const a1 : ([string] | [string, number]); fn(a0, ...a1);...

This is a fun one because we get a new error message: ``` declare function fn(p0: number, p1?: string, p2?: number) : void; declare const a0 : number; declare const...