That is akin to saying using a GC is giving up on safe memory allocation, and the borrow checker is the only solution to a complex problem. Exceptions are handled gracefully in real world projects as well, otherwise Python, Java etc would have died a long time ago.

▲

tcfhgj 4 days ago | parent | next [-]

Maybe you are not giving that up, but you are giving up doing memory management "properly", i.e. use more memory and CPU time than necessary for convenience.

▲

nromiun 4 days ago | parent [-]

Like writing only in assembly is "proper" programming? Using more memory and CPU time than necessary for convenience?

▲

tcfhgj 4 days ago | parent [-]

systems programming languages compile right down to machine code

▲

nromiun 4 days ago | parent [-]

Both borrow checker and GC use malloc/free internally as well. According to you there is no difference between the two.

▲

tcfhgj 4 days ago | parent [-]

yes, there is: GC will not use stack allocation and it will add another layer of memory management resulting in significant memory overhead (runtime overhead)

▲

nromiun 4 days ago | parent [-]

Of course they do. For example C#, D, Nim etc all use stack allocation with their GC.

Not to mention Rust also allocates dynamic objects on the heap. So not sure what is your point.

	▲	tcfhgj 3 days ago \| parent [-]
		The language may allow it, but it's not GC managed then. My point is runtime overhead. In C# structs and their refs (including a simple borrow checker to detect invalid ref use) were introduced to escape GC management und reduce it's runtime impact on the programs

▲

csullivannet 4 days ago | parent | prev [-]

Maybe this is my Golang dev leaking, but I intuitively thought that `try: / except:` in Python is essentially the same thing as `if err != nil`, just my IDE doesn't scream at me if I don't catch them.