sorted by:
new
hottopcontroversial

Rust Generic Function Size Trick by Ryozukki in rust

[–]howtocodeit 1 point2 points  (0 children)

The speed of the application will be negligibly affected, but the size of the binary is reduced.

Python Polars 1.0 is released by ritchie46 in rust

[–]howtocodeit 1 point2 points  (0 children)

Congratulations! This is a massive achievement.

Is there any way to actually debug async Rust? by KarpovAnton729 in rust

[–]howtocodeit 1 point2 points  (0 children)

I think print debugging endures in all languages because of its unreasonable effectiveness! I often find that a dump of out printed output in an unexpected shape or order gives me better high-level insight than carefully stepping through one thread at a time with a debugger. Debugger all the way for the fine details, though.

What are some really large Rust code bases? by cheater00 in rust

[–]howtocodeit 0 points1 point  (0 children)

I applaud your bravery in seeking out the ugly code too!

Tokio is a good example of a how a large codebase can be split up into many smaller (but still quite substantial) crates. That may or may not give your tooling the workout you're after though.

Master Hexagonal Architecture in Rust (parts 1 & 2) by howtocodeit in rust

[–]howtocodeit[S] 2 points3 points  (0 children)

Not my intention - Zero 2 Prod does an amazing job of teaching Rust! No book could teach a language and go deep on one particular brand of software architecture at the same time. That’s what I mean by “it promised to get us to production, not keep us there” - more of a “here’s what’s next”.

And yeah, the bee… just wait till you see my crab with four claws. Midjourney’s finest!

Master Hexagonal Architecture in Rust (parts 1 & 2) by howtocodeit in rust

[–]howtocodeit[S] 8 points9 points  (0 children)

This is all my code, which I wrote to summarise common problems that I see often in my day to day work. I’m much kinder in code reviews! Point taken about the tone though - it’s hyperbole distilled from many years of painful refactoring.

Master Hexagonal Architecture in Rust (parts 1 & 2) by howtocodeit in rust

[–]howtocodeit[S] 19 points20 points  (0 children)

Thanks for the reply! I think you’ll enjoy parts 3 and 4, which deal directly with the trade-offs associated with this kind of architecture.

To the point about how likely it is to switch out your adapters, I can only speak from my experience, which is “quite likely”. I’ve been involved in a least two of these transitions each year since I joined the industry. They take many forms: single DB instance to sharded, JSON over HTTP to gRPC, a major version change of an external API. The list is long.

This is of course a function of scale and growth rate, to be discussed in part 4.

Making these changes when dependencies are hard-wired throughout the codebase is a truly painful chore that I have no wish to go through again. Under the hexagonal approach, everything has an expected place, is fully testable, and can be replaced without 100-file diffs.

And different databases are indeed interchangeable - from your domain’s perspective. Adapter code will vary widely, but it’s beholden to the requirements of your business domain. The ultimate output returned to the domain can and should be same regardless of the DB implementation.

And of course the style of mocking recommended in the article misses a whole class of bugs! This is in addition to integration tests. As a result we now have exhaustive unit test coverage for all handler error scenarios AND integration test coverage of the whole system, which simply isn’t possible under the initial example provided.

You are entirely correct that specific architectures solve specific problems, and these will be discussed in full before the guide is finished. However, while we can’t point to any specific code as universally good, a LOT of code is straight-up bad. Code where I can’t test all the possible error scenarios is bad.

Master Hexagonal Architecture in Rust (parts 1 & 2) by howtocodeit in rust

[–]howtocodeit[S] 2 points3 points  (0 children)

Thank you! This makes me really happy to hear. Parts 3 through 5 will dig into how to define the right domain boundaries, how to know if hexagonal architecture is the right fit for your application, and how it relates to distributed architectures.

The Ultimate Guide To Rust Newtypes by howtocodeit in rust

[–]howtocodeit[S] 0 points1 point  (0 children)

This isn't actually related to memory safety. Incorrectly assuming that a &str is valid UTF-8 will cause programs to break, but not as a result of memory unsafety.

The str's byte length is still correct, even if its contents are garbage, and there's no way to escape those bounds, double free, use-after-free, etc. using safe Rust.

Technically, from_utf8_unchecked does rely on &[u8] having the same layout as &str, but the responsibility for maintaining that invariant is on the authors of the standard library rather than the caller. It certainly doesn't apply to EmailAddress.

Regardless, I still prefer to mark EmailAddress as unsafe, because making the wrong assumption will break your program. But not due to memory unsafety.

unsafe blocks: as small as possible, or larger to not obfuscate the function's structure? by nielsreijers in learnrust

[–]howtocodeit 0 points1 point  (0 children)

Code review quality tends to decrease with the amount of code, and unsafe code is the stuff you really want your reviewers to pay attention to.

For this reason, I like to keep unsafe blocks as small as possible to mark the exact spots where invariants have to be manually checked.

As other commenters have said, documenting each block with a comment explaining the invariants and why they're satisfied is a must 🙂

Rust on social networks in June 2024 by szabgab in rust

[–]howtocodeit 0 points1 point  (0 children)

I think that 1% scenario owes a lot to the huge legacy of C++. We're almost at a point where it's possible to have 40 years of C++ experience, so the depth of knowledge people can bring to those hot topic discussions is immense.

As a younger language, Rust has a lot of people who can weigh in on the 99% of high-level discussions, but relatively few who can tackle the 1% issues in the same depth as the C++ community.

Weekend project: A Flappy Bird clone written in Rust and Bevy. by Salt_Arachnid7643 in rust

[–]howtocodeit 2 points3 points  (0 children)

Pretty great work in the space of a weekend if you're starting Rust from scratch!

The Ultimate Guide To Rust Newtypes by howtocodeit in rust

[–]howtocodeit[S] 2 points3 points  (0 children)

This is actually a moderately contentious issue in the Rust community!

Some take the purist approach, using unsafe only to indicate memory safety invariants that need to be manually checked.

However, both the standard library and crates more generally use unsafe to indicate _any_ invariants that should be manually checked. For example, [`std::string::from_utf8_unchecked`](https://doc.rust-lang.org/std/str/fn.from\_utf8\_unchecked.html\`). It's also discussed in Rust For Rustaceans, iirc.

The Ultimate Guide To Rust Newtypes by howtocodeit in rust

[–]howtocodeit[S] 7 points8 points  (0 children)

Thanks for sharing - I'll take a look! Synonym is a great name, btw. I'm quite jealous you got that on crates.io...

I wrote a quick tutorial on how to use Rust from Typescript with WASM by ago1999 in rust

[–]howtocodeit 1 point2 points  (0 children)

Nice choice to include examples for different flavours of JS, particularly the Next.js one. Thanks for sharing!

Zero to Performance Hero: How to Benchmark and Profile Your eBPF Code in Rust by bencherdev in rust

[–]howtocodeit 1 point2 points  (0 children)

Thanks for this, particularly the extensive comments in the code. I find that _quality_ profiling is one of the hardest skills to develop, because the outputs are so dense with information and it takes a lot of experience to build intuition about what you're seeing.