The Rust toolchain is ready for production use

[Dana Jansens]

Dear Chromium Community,

As of M119 Chromium's Rust toolchain is production-ready.

For the projects that are underway already that are making use of Rust libraries, we are happy to say toolchain support is no longer an obstacle to shipping. Chrome M117 has a Rust library in Stable that is being used daily on Android, Mac, Windows, and Linux. And Chrome M119 Beta has the same on ChromeOS.

We’re now confident that the toolchain is capable of integrating well with Clang in our build configurations and that the resulting binaries optimize well, run correctly, and interact with crash reporting and gdb/lldb properly. From agl@: Our experiment to switch the QR code generator over from C++ with IPC to synchronous Rust has gone smoothly with nothing breaking.

We will address any issues that come up in the future, and we greatly welcome feedback about sharp edges that you uncover at rust...@chromium.org.

At the moment, Rust is approved by Chrome ATLs for use in certain third-party scenarios. We're excited to use learnings from this to inform ongoing discussions around potentially leveraging Rust more widely in Chromium.

Cheers,

The Rust Toolchain / Chrome Memory Safety Team

[Dominik Röttsches]

Hi Dana, Adrian and the whole Chrome Memory Safety Team,

Congratulations on this fantastic milestone! Tremendous effort on communication, evangelizing and technical excellence in delivering a solid and thorough technical foundation for Chromium to deliver Rust components. Well done!

Dominik

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAHtyhaTuZoMQ_m5shwZgPRBF7C2izyvYCPpO3hfLpKbRG4iiug%40mail.gmail.com.

[Caleb Raitto]

Congratulations on this incredible milestone!

Does this mean that the Rust JSON parser [0] can be used in production soon?

[0] https://source.chromium.org/chromium/chromium/src/+/main:services/data_decoder/public/cpp/data_decoder.cc;l=196;drc=f5bdc89c7395ed24f1b8d196a3bdd6232d5bf771 

Thanks for all your hard work on this,

-Caleb

[Dana Jansens]

Hi Caleb,

Thank you :) The JSON parser is still in an experimental phase, so there's no timeline or guarantee I can give about that at the moment.

Cheers,

Dana

[Caleb Raitto]

Understood -- thanks for the update. Still very exciting to see the progress here :)

-Caleb

[David Adrian]

We should have the Rust JSON parser enabled on Canary/Dev soon.

--
You received this message because you are subscribed to the Google Groups "rust-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rust-dev+u...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/rust-dev/45cabf3b-fcc5-4675-b46e-db4bc24c522en%40chromium.org.

[Caleb Raitto]

+pauljensen@

-Caleb

[Paul Jensen]

On Fri, Oct 20, 2023 at 1:33 PM Caleb Raitto <cara...@chromium.org> wrote:

On Thu, Oct 12, 2023 at 12:27 PM David Adrian <dad...@google.com> wrote:

We should have the Rust JSON parser enabled on Canary/Dev soon.

This is incredibly exciting.  Over on the Protected Audience team, we're frequently running into DataDecoder latency.  We've spent a lot of time optimizing this, e.g. 1, 2, and are likely to spend a lot more time on this.  If switching to a Rust JSON parser cuts down on process-creation and IPC for the DataDecoder, that would be really helpful.

[Paul Jensen]

Dana,

Ping 10 months later.  How's this going?