Max Bruckner
Max Bruckner
Aaargh! Their library puts all my keys on the heap instead of using the specified arena allocator. Seriously?
Maybe they [fix it at some point](https://github.com/google/protobuf/issues/1896), but 🤷. I'll still be using their arena allocator but use it with protobuf-c.
I am writing molch for the startup 1984not GmbH which is making an end to end encrypted messenger app for mobile phones. I would still consider the app to be...
I can't use this library without that feature at all! I use an arena, because I store sensitive key material in my protobuf messages and I provided an allocator with...
> We are thinking about how to expose aliasing but we want to be careful and expose the right API. That makes sense, especially without `std::string_view`/`std::span`
The only way to go for Google would probably be abseil, but that doesn't go well with semantic versioning.
This has been stable since rust 1.55 at this point.
~~Although this changelog entry confuses me: https://github.com/bytecodealliance/wasmtime/blob/main/RELEASES.md#200~~ ~~Apparently `wasmtime` *does* have support for `riscv64` :thinking:~~
Nevermind, you're using `wasmer`, not `wasmtime`.
Is this still an issue in `sqlx` `0.8`? It seems fixed for me.