4 ms·
> Mismatched type definitions in different translation units caused an implicit 32 to 16 bit conversion. Rust would not have failed to compile at step one nece
by humanrebar 4y ago
> Mismatched type definitions in different translation units caused an implicit 32 to 16 bit conversion.
Rust would not have failed to compile at step one necessarily. Or were you assuming a full revamping of the build and dependency management systems in addition to the rewrite of the program itself?
If we need to clean up the build and dependency management system to start using Rust correctly, isn't that two major migrations?
- briantkelley 4y ago> Rust would not have failed to compile at step one necessarily. True. In this case there was old code and new code. I assumed in a hypothetical hybrid Rust codebase, bindgen would be used to bring the types in old code to Rust, so the compiler would identify the type mismatch in perhaps the impl From. > If we need to clean up the build and dependency management system to start using Rust correctly, isn't that two major migrations? At the scale of Office, managing the build system is an evergreen project staffed by dozens of engineers. Adding support for Rust integration is a typical deliverable for such an org.