4 ms·
While the other commentors are correct that there's no Rust foundation, it is true that a member of the Fuchsia team is on the Rust language team, which does de
by steveklabnik 7y ago
While the other commentors are correct that there's no Rust foundation, it is true that a member of the Fuchsia team is on the Rust language team, which does decide the direction of the language.
It was very much a pro for our users; like any open source project, we need contributors who are willing to help do the work. Fuchsia's experience with async/await was really important to validate that the design worked well; for example, many people think of it as a feature that's useful for web servers only, but Fuchsia demonstrated its validity in other contexts. Beyond semantics, it also helped with syntax; https://github.com/inejge/await-syntax https://github.com/inejge/await-syntax was created during the debate about "prefix await," and was able to show us what a few variants of the syntax would look like in real-world code.
> If this is the case, I don't like it very much... That would be a Pro for C, or whatever language out of their reach (as in The Fuchsia project doesn't have the opportunity to influence the evolution of the language).
C has a standards process that anyone can get involved in, following ISO rules. Google is a major player in the C++ standards process too.
- scoutt 7y agoThank you for the explanation. I wasn't so wrong after all. Perhaps it was the wording that made me think that way... "To influence". I would rather prefer as you wrote; to collaborate or to contribute. Time will tell...