The usual handling in Rust afterwards is in most cases log one error or return to upstream “there was an error”. In some rare cases all errors returned as a single case.
Both of these first are bad for i18n and finding what’s really happened in the middle.
In that for, all error messages have been lost. If to add such output “for” is the most elegant solution.
Next step is to make it fully native, without any web view
It’s weird. Language support is weirder. Zed devs decide what language constructions are acceptable, and which are not.
I don’t think cargo-deny alone is enough. And many from Rust ecosystem thinks that if I specified version “1”, it will be enough forever. Many tools nowadays are installed by binstall, so binary will be older and older and won’t receive any updates.
I would still prefer Rust over C++ even in GamrDev.
Deku is a declarative binary parser. deku_string is an extension which currently provides utility wrappers for data vectors and unicode strings, which can be prefixed or fixed length. Additionally library provides support for 7-bit encoded integers from .NET.
For example, I often work with binary structures where strings are either length prefixed (with zero character in a buffer) or in fixed size buffer with a zero-ended sting inside.
There’s multiple examples with custom writer and reader functions, which work, but are less convenient to use.
Any additional ideas for utilities are welcome.
I already have mine written quite a while ago. Why not obsidian? AsciiDoc and few other things Obs will miss. Works with SQLite and PostgreSQL. For pure native UI (not WebUI) miss only AsciiDoc grammar I’m working on.
For you… sql knowledge requirement depends on your likings: you can build very small or unoptimised app and be fine, you can make very nice, and complex one and have very complex SQL queries.
I discourage to use MySQL (and clones) due some… peculiarities.