Rust

Rust

Discussions about the Rust programming language

Will pfp

Rust 1.83 has been released with a bunch of extensions to const functionality, as well as the usual API stabilizations: https://blog.rust-lang.org/2024/11/28/Rust-1.83.0.html

0 reply

5 recasts

25 reactions

Agost Biro pfp

I’ll definitely learn other languages in the next 1-2 decades for fun, but I fully expect Rust to be my daily driver in this period

2 replies

0 recast

8 reactions

Agost Biro pfp

If you're unsure about a type, just write `bool` and let the compiler tell you what it really is

0 reply

0 recast

3 reactions

Alfie John pfp

When in doubt, wrap it in Arc<>

0 reply

1 recast

0 reaction

Agost Biro pfp

In general, it's helpful to think about an `Option` as container with 0 or 1 elements and a `Result` as a container with exactly 1 element where the contained type is a sum type.

0 reply

0 recast

1 reaction

Agost Biro pfp

Results and options can be difficult to compose. Fortunately the `transpose` method makes this a breeze. E.g. if you're mapping over an option and need to return a result, you can just call transpose on the `Option<Result>` returned by `map` and propagate the error from the outer scope with `?`.

0 reply

0 recast

0 reaction

christopher pfp

Finally conquered the last bits of the contract flow from Golang to Rust.. 1. Alloy macros are pretty great. Using Solidify contract interfaces directly in Alloy functions is also pretty great. Foundry fuzzing and property-based testing also great. 2. Geth contract middleware is still more ergonomic than Alloy, e.g. waitForTransaction doesn’t exist. 3. Rust Result typing is way better for flow state and DRY. 4. You should use Rust if you need transaction certainty. But it is totally overkill for smaller projects and hackathons.

1 reply

0 recast

3 reactions

Agost Biro pfp

Most people: rustc error messages are great, because the compiler gives you actionable advice! Me: hehe, compiler said turbofish > error: generic args in patterns require the turbofish syntax

1 reply

0 recast

3 reactions

christopher pfp

Linus, Re: Rust Kernel Policy 😳 “You are saying that you disagree with Rust - which is fine, nobody has ever required you to write or read Rust code. But then you take that stance to mean that the Rust code cannot even use or interface to code you maintain. So let me be very clear: if you as a maintainer feel that you control who or what can use your code, YOU ARE WRONG. I respect you technically, and I like working with you. And no, I am not looking for yes-men, and I like it when you call me out on my bullshit. I say some stupid things at times, there needs to be people who just stand up to me and tell me I'm full of shit. But now I'm calling you out on *YOURS*.” https://lore.kernel.org/rust-for-linux/CAHk-=wgLbz1Bm8QhmJ4dJGSmTuV5w_R0Gwvg5kHrYr4Ko9dUHQ@mail.gmail.com/

1 reply

0 recast

5 reactions

Will pfp

Rust 1.85 and the Rust 2024 edition have been released: https://blog.rust-lang.org/2025/02/20/Rust-1.85.0.html

1 reply

0 recast

2 reactions

Agost Biro pfp

Really good 30 minutes overview of topics that experienced programmers usually find challenging with Rust https://www.youtube.com/watch?v=8-KLX1PGg8Q

0 reply

1 recast

2 reactions

christopher pfp

Really great crate for wrangling config vars. WAYPOINT_HUB__URL="..." will easily map and bind to config.hub.url, for example. https://github.com/SergioBenitez/Figment

0 reply

1 recast

1 reaction

MetaEnd🎩 pfp

when you run cargo cache -a for the first time Size changed 17.09 GB => 5.39 GB (-11.70 GB, -68.47%)

0 reply

0 recast

2 reactions

christopher pfp

Rust. Rust. RUST. RUST! RUST! RUST!

1 reply

0 recast

7 reactions

Will pfp

Rust 1.84 has been released: https://blog.rust-lang.org/2025/01/09/Rust-1.84.0.html

1 reply

1 recast

4 reactions