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.
You have to provide source to a rust repository. Otherwise, it’s impossible to compile and link Rust safely. There was an article in the topic.
Long story short you can prepare and link a binary library, but you can’t guarantee any type safety or additional optimisations.
Quick analysis of code shows that there’s no suspicious build scripts or imports added, just an additional poorly documented and not tested function.
Documentation is additionally published to a third-party website.
Repository is probably is hidden which is ok.
Why you’ve wrote “dont sign in…” for GitLab? GitLab is safe
I’ve forgot slint. Same as QT
Currently I use WxWidgets and Cocoa for macOS.
The best would probably be pure native UI with static/dynamic library in Rust for logic. Sounds hard, but it’s the best option in my opinion.
My 2 cents is below. Your decision depends on your tasks, preferences and targets.
It’s a good suggestion
Integer sqrt can be used for integers with any length, not only for integers fit into f64
Integer sqrt is usually not a library function and it’s very easy to implement, just a few lines of code. Algorithm is well defined on Wikipedia you read a lot. And yes, it doesn’t use FPU at all and it’s quite fast even on i8086.
Algorithm is so plain and simple, it doesn’t require nightly or Rust specifically to implement.
Nice article, I enjoyed it. Why float sqrt has been used? Integer sqrt is way faster and easily supports integers of any lengths
Could you please explain why he should be embarrassed by such post? What would you improve?
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.