intrepidpeach.bsky.social
An American living in the UK. I like hiking with my dogs and software development. I eat far too much chocolate, too
28 posts
59 followers
197 following
Regular Contributor
Active Commenter
comment in response to
post
Godspeed!
comment in response to
post
That looks sick. I also would like to be able to do that
comment in response to
post
You should be able to pattern match on slices
comment in response to
post
How do you find the chapter on buffer/memory usage? Is it useful?
comment in response to
post
Then every time you need to know the size of the array you’d need to recheck it. Sounds expensive, but to each their own.
comment in response to
post
I think it depends on the mode you want RustRover to operate in. Either as a single file editor or something more comprehensive and project oriented.
comment in response to
post
Does the book get into any advanced topics? Like what to use instead of free lists?
comment in response to
post
One day Bluesky will add edit capabilities and I will be so happy
comment in response to
post
No shade here, genuinely curious: why would you ever want sentinel terminated arrays ad they’re the main cause of buffer overflow vulnerabilities?
comment in response to
post
RustRover needs to open the containing directory to understand the project correctly.
www.jetbrains.com/help/rust/qu...
comment in response to
post
I can’t recommend build-your-own.org/database/ enough. The code is in Go, but everything is concise and easy to understand
comment in response to
post
Another vote for undefined behavior. I could stomach and handle almost every wart C has except for undefined behavior. It’s everywhere. It’s invisible. It’s compiler version dependant. It’s build profile dependant.
The compiler knows why the code is wrong, but god forbid it tell you
comment in response to
post
I hope it was more like when Macron crushed Trump’s hand in his first term.
comment in response to
post
We moved to the UK for similar reasons
comment in response to
post
Please forgive my curiosity, but I’d love to know which memory layout you decided on when representing the hex board.
comment in response to
post
Oh no. A simple compile time error. One where the compiler provides ample diagnostics to understand and fix the error. The horrors
comment in response to
post
In this case there’s no indirection. Every inner type is a concrete static type. There’s no runtime that checks which functions are there. Just function addresses to the statically compiled functions.
comment in response to
post
Where’s the code? I’d love to take a look. I also haven’t beaten Cave Story :D
comment in response to
post
Yea! Miri is a godsend!!
comment in response to
post
I write code in Rust for the joy of solving problems in Rust. If I wanted to write C or use C libraries I would have done so already
comment in response to
post
You’ll get there. The biggest thing you eventually understand is how the design of data structures and code impacts how difficult they are to make and maintain in Rust.
Learning this is an iterative process and one I find worthwhile. I’ve become a better architect and coder because of it.
comment in response to
post
You can do the same in Rust stackoverflow.com/questions/47...
comment in response to
post
So something like crates.io/crates/num_e... ?