Rust and C++ Interoperability in Chrome

Re:Rust and C++ Interoperability in Chrome by jcranmer on Wednesday August 19, 2020 @02:35PM (#24214234)

It's also worth mentioning that Mozilla tends not to use a lot of standard C++ types, using nsTArray instead of std::vector or nsA?C?String instead of std::string. This makes the porting of APIs using arrays or structs easier, since Mozilla owns the ABI rather than needing to worry about different standard libraries having different ABIs.

[ Parent | on HN ]

Re:Rust and C++ Interoperability in Chrome by ChrisSD on Wednesday August 19, 2020 @02:51PM (#24214512)

C++ interop with C++ can be a pain. E.g. even with the same version of the same compiler, GCC can have different options enabled that affect the layout of some types.

[ Parent | on HN ]

Re:Rust and C++ Interoperability in Chrome by ncmncm on Thursday August 20, 2020 @12:14AM (#24219820)

That is the same in all languages mature enough to have variant options. Rust included.

Therefore, a tendentious distraction from the topic. Chris, I shall expect better from you in the future.

[ Parent | on HN ]