296
Learning to program in rust (programming.dev)
submitted 1 year ago by to c/programmer_humor@programming.dev
58 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 37 points 1 year ago (3 children)

Call me a weirdo but the more errors a compilers give me the happier (albeit a bit frustrated) I am. That stuff generally surfaces in a way or another… and I prefer at compile time 🙂

That said I haven’t spent quality time with Rust yet… so not sure if there are a lot of nitpicks (ala go) or these are valgrind-level of “holy s*** I am so grateful to this tool” 😃

  • permalink
  • fedilink
  • source
  • hideshow 3 child comments
    •
  • [–] 6 points 1 year ago (2 children)

    The borrow checker makes things a bit more complicated to get running, definitely takes some getting used to when you come from a non-memory safe language. But the compiler is really helpful throughout almost all mistakes, often directly providing an explanation and a suggested fix. One of my favorites programming experiences so far

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 1 year ago* (last edited 1 year ago) (1 child)

    ...definitely takes some getting used to when you come from a non-memory safe language...

    I actually think it's more like the opposite. The compiler takes the normal rules you apply to avoid issues with a non-memory safe language like C/C++ and enforces them explicitly where memory safe languages don't have those rules at all. I think lifetimes are much more confusing if you've never dealt with a user after free and usually let GC deal with it.

    Also yes the compiler warnings and errors are amazing, the difference between rustc and gcc is night and day.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 1 year ago* (last edited 1 year ago)

    I can confirm, I've never used a non memory managed language, and the Rust borrow checker is a massive kick in the teeth

    But, the more i consider it from the perspective of memory, and pointers, the borrow checker makes a lot of sense

    Especially when storing references inside structs, and how mutability affects references

    I actually figured out i could fix a re-mutable borrow error by performing the two mutable operations in separate for loops

  • permalink
  • fedilink
  • source
  • parent