Folkert de Vries

yeah, this needs more work because right now we drop too much code apparently and then in `borrow.rs` we're missing specializations. Really not sure why this is a problem for...

well so what this does now is report the error twice, do we want that? [see this comment](https://github.com/rtfeldman/roc/issues/1708#issuecomment-928444714)

we concluded earlier that the problem is insufficient dead-code elimination. The `roc_alloc` function and its friends are not actually used by the compiler code. On *nix systems that means the...

to get the `cli` to compile you now need to disable `repl_expect` and add some definitions to `cli/src/lib.rs` to satisfy the linker ``` use core::ffi::c_void; /// # Safety /// The...

fixed by #3901 `cargo build` works on that commit. It's not in CI yet so some things may break again. We'll try to at least get a `cargo check` CI...

Figured out that the issue with `Derive.roc` is due to a problem with continuations. It's unclear whether it's an issue with our encoding or with morphic itself. issue on the...

yes

I did some digging. The relocation in question is [crates/linker/src/lib.rs:2788] &rel = ( 26934, Relocation { kind: Relative, encoding: Generic, size: 32, target: Symbol( SymbolIndex( 587, ), ), addend: -4,...

The issue seems to be a bit more general. Likely there is a `catch` that just catches all exceptions and lets the decoder return `Nothing`. For instance, a `Debug.todo` will...

I made a micro-benchmark to check two bounds-checking strategies: if-statement to check the bound up-front, and a try/catch that catches the out of bounds RangeError. See [the discourse post](https://discourse.elm-lang.org/t/benchmarking-overhead-of-bytes-bounds-checks/3128/4) for...