Yorick Peterse

I _sort_ of made some more (interesting) progress: Rust's musl target bundles a static libunwind library in `~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-musl/lib/self-contained/libunwind.a`. If I inject that as an argument after the runtime, I can...

https://github.com/rust-lang/rust/blob/62d7ed4a6775c4490e493093ca98ef7c215b835b/compiler/rustc_codegen_ssa/src/back/linker.rs#L775 suggests we need to pass `--eh-frame-hdr` when using musl-gcc. Removing this option from the musl-clang output reproduces the lack of a stack trace.

For musl, what we could do is this: the runtimes we build aren't just gzipped `.a` files, but `.tar.gz` archives. We then extract those into `~/.local/share/inko/VERSION/runtimes/TARGET/`. For musl, we include...

I got linking with musl to work, so we can at least build executables that target musl now. Building the compiler on Apline is still broken though, as https://gitlab.com/taricorp/llvm-sys.rs/-/issues/44 hasn't...

@thaodt Modifying the AST/HIR isn't necessary nor wanted. Looking at it a bit more in-depth, I think the best place to do this is actually at the MIR level, not...

@thaodt Thank you for initially looking into this. With the release of 0.14.0 closing in I'd like to include this feature in the release, so I'll take a look at...

PGO is something that indeed can be useful at some point in the future, though it will likely also require us to host pre-built binaries so others can take advantage...

My guess is that when we destructure an owned value as part of a match, we forget to insert a ref count check.

The following program shows the problem: ```inko import std.stdio.STDOUT class Person { let @name: String fn greet { STDOUT.new.print("Hello {@name}") } } class async Main { fn async main {...

IIRC there's still no 64-bits WASM, which the VM requires. I doubt we'll see this any time soon, and WASM isn't really of interest to me at this point. As...