Gotcha, fair enough. So, there is no direct influence on the generated code, like how a multi-pass compilation process can build a more complete image of the program for more aggressive optimizations?
I'm just starting to graduate past interpreters into compilers and still don't have a full grasp of the end-to-end picture.
Great point about all these massively used tools being written in C or C++, but then I'm still not sure why, say, Rust has chosen this route. I totally get the dogfood argument, but I still feel like that sounds like a side-project that could dictate ongoing development, not the canonical implementation.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Gotcha, fair enough. So, there is no direct influence on the generated code, like how a multi-pass compilation process can build a more complete image of the program for more aggressive optimizations?
I'm just starting to graduate past interpreters into compilers and still don't have a full grasp of the end-to-end picture.
Great point about all these massively used tools being written in C or C++, but then I'm still not sure why, say, Rust has chosen this route. I totally get the dogfood argument, but I still feel like that sounds like a side-project that could dictate ongoing development, not the canonical implementation.