AD Controls Department » Central Services Group » Protocol Compiler

Added: 66acdb6a

This is a preliminary implementation; I fully expect further changes to the API as Rust users find deficiencies in the code. I encourage Rust programmers to look at the generated code and recommend changes to the API which improve correctness and to offer optimization suggestions.

Re-opening for feedback.

After some more reading and research into Rust, it seems the crate that provides the official, asynchronous API is tokio. If/when we develop an ACNET crate, it'll probably be based on this API. The tokio crate has lots of useful, asynchronous constructs including traits for encoding and decoding protocols! I think it may be a good idea to retool the protocol compiler's Rust support to use these traits. My only hesitation is doing this would make Rust the first language dependent on a third-party library¹. Installing third-party crates is insanely easy (at least on my Mac), so it doesn't seem like this is too much of a hardship. Plus, there's talk the tokio implementation might become the async/await core for Rust which means, in the future², we won't be using a third-party crate.

Any thoughts, Brian?

¹ We do have a GWT generator, but it's a specialization of the Java generator. The generic Java generator doesn't have any third-party dependencies.

² But I don't want to await on that Future. Ha! A Rust joke!