Re:Writing Pythonic Rust
by nicoburns on Monday May 24, 2021 @07:00PM
(#27270683)
I guess someone coming from only C might not have encountered closures, but most languages have them these days (modern javascript code uses them everywhere), and I don't think they should be considered especially advanced. "How do closures work?" Was a question I was expected to know how to answer when going for my first ever junior programming job with zero professional experience (and no CS degree either).
[ Parent
| on HN ]
Someone coming from C also would certainly know about the difference between the stack and the heap too, so it's a little strange to me that GP called that out
Why?
A lot of embedded code NEVER calls malloc (thus the need for no_std in Rust). Consequently, you can go a long way in embedded without really knowing the difference between stack and heap.
"Embedded programmer" does not imply "Linux Kernel Hacker".
Re:Writing Pythonic Rust
by throwaway894345 on Monday May 24, 2021 @08:42PM
(#27271451)
There’s a pretty wide chasm between kernel hackers and people who have used malloc before. :) And an embedded programmer ought to have the ability to intuit (a naive) malloc on their own (you can have malloc without a kernel).