4 ms·
> Porting to rust is easier if it doesn't require a person to be an expert at two different kinds of inline assembly syntax. Sadly, this doesn't save you from
by steveklabnik 7y ago
> Porting to rust is easier if it doesn't require a person to be an expert at two different kinds of inline assembly syntax.
Sadly, this doesn't save you from that, in fact, it can be argued that the string syntax is what makes you need to learn a whole second set of syntax. This is due to clobbers.
> There is also the issue, I'm sorry, of the rust preprocessor. It will be written and it will be used.
I don't forsee this happening; Rust has powerful enough generic capabilities that even with tens of millions of lines of Rust existing today (I'd actually guess we're in the hundreds right now, but still), nobody has invented one yet. Getting away from the pre-processor is considered a pro, not a con.
- pjmlp 7y ago> Getting away from the pre-processor is considered a pro, not a con. Yep, even ISO C++ is putting energy into making each standard revision one reason less to use it.
- jcelerier 7y ago> nobody has invented one yet. no need to invent one when cpp exists and works. I've seen people use it in Java, and it is sometimes used in unix config files (e.g. .Xresources).
- steveklabnik 7y agoSure; I'm not aware of anybody using cpp with Rust either.