sabine

Criteria to evaluate performance issues: 1. does it block the language from compiling to WASM GC by repurposing their current compiler implementation? 2. does it make the resulting code much...

@RossTate I believe that, in the interest of getting a reasonable WASM GC MVP out of the door, it is very important to focus on resolving performance issues that trigger...

Fair enough, (4) is close enough to (1) to look like the next best solution in terms of effort needed and we could use `i32` arithmetic. I'll look into this...

I'm wondering if I can do this by first compiling to "WASM GC MVP with i31ref" and then translating that code to "WASM GC MVP without i31ref". At least, this...

> As a bystander who follows these threads I wanted to share some feedback that this aggressiveness is quite off-putting. I don't think anyone contributing here wants to come off...

@RossTate > if we do change the number of bits for guaranteed-unboxed integers, what's a non-arbitrary number to change it too? I don't think that a non-arbitrary number of bits...

Not 100% sure the detailed check for `opam>=2.1.0` works in all compilation environments, please take a careful look, or be prepared to change to a simpler (but not fully accurate)...

I'm fetching data from an API in `_layout.svelte` to share that between different sub-routes. It seems I've been running into this issue. Is someone aware of a workaround? Edit: My...

Here's a simple (but admittedly impulsive/careless) way how new users end up with a broken switch: 1. User starts running someone else's instructions that happen to create a switch 2....

> What about prompting a link to a [FAQ](https://opam.ocaml.org/doc/FAQ.html) entry that summarises all cases (switch to remove and checkout new branch for the moment). The message will be cleaner and...