实时更新 /r/rust 热门的话题。对于 Telegram 的用户可以订阅 Telgram Resource Channel 获取同样的咨询更新。
Inspired by this post I wrote my first proc-macro!
I mashed together my interests in procedural graphics generation and Rust programming for this experiment. I implemented the boids flocking algorithm to create swirling patterns. The implementation is heavily inspired by Sebastian Lague's coding adventure with boids video. Here's a small demo.
It is common convention for code to use
FIXME as notices within the code, which can easily be found with a
rg 'TODO|FIXME'. I propose a new convention for Rust code specifically:
BLOCKED to signify code that will be changed once a certain feature has landed on stable. Its usage looks like this:
I've been thinking of building a new desktop system – first time in years. Being a Rust enthusiast, a relevant question is: how fast it's going to compile Rust code? I have been thinking of building the system around a Ryzen 3900X 12-core processor and 32 gigs of RAM. However, I'm still a bit undecided whether to go all in and one-up it to Ryzen 3950X (16-core). I suspect that's where the diminishing returns are starting to erode the bang-for-the-buck-factor. But if it's still noticeably faster, that's like paying for a good reason.
We just released Goose 0.7, introducing async support. Goose is a load testing framework inspired by Locust. Where in our testing an optimized Locust test plan was able to generate nearly 20Mbit/s of HTTP traffic, the equivalent test plan in Goose is now able to sustain ~220Mbit/s of traffic, all from a single core! (Prior to adding async, in the same configuration Goose was generating ~110Mbit/s of traffic).
Here is an example: [playground]
Welcome once again to the official /r/rust Who's Hiring thread!
Over the weekend, the contents of an internal Gitlab instance from Daimler (Mercedes) was leaked. It contains, among other things, the source code of their internal "onboard logic unit" (OLU) software systems for Mercedes vans.