Recent searches
Search options
Administered by:
#Rust
https://www.wacoca.com/games/1129089/ 無言で「Get Wild」を弾くルーナに爆笑するみこちとスバル「holoRUST」面白まとめ【さくらみこ/大空スバル/姫森ルーナ/ホロライブ切り抜き】 ##GAMING ##さくらみこ切り抜き ##みこち切り抜き #Game #GameNews #games #GamingNews #GamingTrending #rust #TrendingGames #Vtuber切り抜き #ゲーミング #ゲーム #ゲーム攻略 #ゲーム最新情報 #さくらみこ #さくらみこ面白い #ドラゴンクエストV天空の花嫁 #ぺこみこ #ホロライブ #ホロライブ切り抜き #ホロライブRUST #ホロライブさくらみこ #ホロライブマイクラ #ホロライブ面白い #みこスバ #みこち #みこち面白い
Gerard 
DeRose 
One of the most off-putting things about #Rust is the complete and utter contempt that most of its community has for #semver: A library that is meant to be used by others should explicitly have a version of 1.0.0 or greater.
0.x.y means that it is not ready for actual productive use:
Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backward compatibility, you should probably already be 1.0.0.Meanwhile in Rust: “The preferred TLS-library with 186k users, 166 contributers, and 3795 commits is still in version 0.23.26.”
Sorry, I’m not going to use a pre-release cryptography library in production! If this is meant for actual use, give it an according version number!
Also, the custom rules are part of the problem: The notion that you should not have breaking changes when going from 0.1.2 to 0.1.3 is explicitly in violation to the rules that semver puts down, yet the rust community has set up expectations that this is not the case.
And then there is of course the entire mess with huge numbers of transitive dependencies for everything. I was looking at a json library and it depends on an “itoa”-crate that literally just exists to convert integers to strings. Aka: it introduces a completely new point where someone can create a dependency that includes malware, for essentially no gain.
Compare this with C++, where the generally preferred json-library has zero dependencies and is in fact single-header-only.
It’s stuff like this that pushes me back to C++ every time I look at rust. Which makes me sad, because I really like many of the high-level ideas behind Rust.
#cplusplus
Mastering Memory Management in Rust: A Deep Dive into Ownership and Borrowing
In the evolving landscape of software development, understanding memory management is crucial, especially with languages like Rust that prioritize safety and concurrency. This article explores the int...
Luna Ch. 姫森ルーナ 
My Easter treat has been to work on my silly hosted-at-home retro website. It now features actual content, animated GIFs, and photos of pineapples!
There's a few dynamic pages under cgi-bin, although they are not actually CGI scripts—they are generated by a Rust program. The dynamic content includes live energy stats, climate info, and memory & uptime info. I still want to fill out the content some more, but I also need to do other things.
Mastering State Machines in Rust: A Deep Dive into Patterns and Implementations
State machines are a fundamental concept in programming, enabling developers to manage complex workflows with ease. This article explores the intricacies of implementing state machines in Rust, showca...
i've just released zizmor v1.6.0!
this release comes with a lot of bugfixes that have accumulated over the last month, plus some big new features:
1. there's a new audit, `forbidden-uses`, which allows users to configure allow/deny policies for third-party actions!
2. the `unpinned-uses` audit has been completely rewritten, and now also supports configuration (e.g. to give your own first-party actions a weaker pinning policy than "must be hashed")
3. there's a new `--format=github` mode, which emits GitHub annotations. these come with quite a few limitations, but may be useful to users who can't use `--format=sarif`!
plus much more; read the full notes here:
