Rewrite it in Rust has always been more a fantasy of the C++ community than a goal of the Rust ecosystem.
While compilation time is a well known Rust pain point, Rust error messages are really one of the best part of the language. Complicated error messages are clearly no a common occurrence unless you rely heavily on…
I'm not sure you can compare the code base of you first program in Go, that is probably small and straightforward, with something as huge and complex as Firefox.
While I would prefer brackets, that would not be enought to solve all the problems since, there would be conflict with array syntax too.
In this case the bug was only for a small subset of the Firefox users (Firefox without x264 support). It doesn't seems impossible to me they missed this specific case.
Rewrite it in Rust has always been more a fantasy of the C++ community than a goal of the Rust ecosystem.
While compilation time is a well known Rust pain point, Rust error messages are really one of the best part of the language. Complicated error messages are clearly no a common occurrence unless you rely heavily on…
I'm not sure you can compare the code base of you first program in Go, that is probably small and straightforward, with something as huge and complex as Firefox.
While I would prefer brackets, that would not be enought to solve all the problems since, there would be conflict with array syntax too.
In this case the bug was only for a small subset of the Firefox users (Firefox without x264 support). It doesn't seems impossible to me they missed this specific case.