blazebra

In that for, all error messages have been lost. If to add such output “for” is the most elegant solution.

Which exactly?

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.

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.

There’s many components which could be split out from this JS engine such as Regex.

I’d love to see how it passes all ECMA tests

And Deno

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