Yip Coekjan

AHH, what can I say... I moved my lookup-cache + regenerate-table code to the end of pass0 (before pass1) and it seems working perfectly. So maybe at least now I...

I am not sure if I solved the problem indeed, as I do not fully understand what the requirements (I mean which fields in the `helper` or something else should...

Now I have to move the "lookup-cache + regenerate-table64" to the end of pass 1. As filling the `table64` depends on some information provided by pass 1. This makes `ls`...

> I'm not sure how you can regenerate tabme64 offset wt pass1, while arm64 (or rv64/la64) offset are known only in pass 3. I did not regenerate `table64` in pass...

> Nope, I didn't planned to do disk-save dynablock before a few version, so there is no infrastructure about that yet. Do we have the full list **in mind** about...

These two days, I suffered from some memory-corruption issue. I am not sure if it comes from box64 or my side. In my design, my external cache system provides a...

> These two days, I suffered from some memory-corruption issue. I am not sure if it comes from box64 or my side. UPDATE: I changed my rust-side malloc backend to...

> However, the memory-corruption issue is still existing. As long as my rust dylib allocates some objects on its own heap, the box64 will have wrong behaviors, resulting in python3.12...

> We use these extensions in a good way, not an evil way. I don't see any issues in box64 side by just using thead extensions. I am not familiar...

If your rust version is higher than or equal to 1.80.0, `cargo install --locked typst-cli` would fail (see #4659). Could you please first check your rust version?