Follow

re: C++ & Rust 

@amiloradovsky@functional.cafe

That's not what I meant. In rust unsafe code is not about the type checks, it's about ownership checks. I'll never turn off type checks, since, unlike ownership checks, they have no cons (and it'll certainly not make my life easier if I did). There is no need to turn off type checks when implementing an efficient intrusive linked list.
Rust's narrative is that the borrow checker is like the type system - universally applicable and superior abstraction framework. I simply disagree with that. It's more like a design pattern as I mentioned, it has pros and cons, and should be optional and better integrated with the language as an optional feature. The mandate of the borrow checker feels as tyrannical to me as that of virtual inheritance in the OOP languages, from the perspective of ergonomics (in many other ways it's certainly not as bad).

@newt

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.