Conversation

@shibao@misskey.bubbletea.dev @privateger@plasmatrap.com i don't think you understand what rust is doing. it isn't detecting situations where issues could occur, it's making situations where issues could occur impossible. for example, you cannot do a use after free in safe rust. you cannot access uninitialized memory in safe rust. you cannot dereference a raw pointer in safe rust. it's not that rust detects you doing these things unsafely, it's that it physically doesn't let you
and yes, there is "manual annotation", because you annotate stuff like types and lifetimes. this isn't python. we can't just let any variable have type, and we do have to unallocate any object a function ends up owning. i don't see how this is bad
and it is doing something similar to haskell. it has ADTs, which makes state significantly safer. a lot of the functional aspects of the language were inspired by languages like haskell
and i have no clue what you're on about with devops or resetting back to valid state. im not sure what im supposed to answer in this rambling here