Gregory's Server@thejpster I'm conflicted about this. Sure it's nice ergonomics, but `cstr!(...)` wasn't that bad, and it feels like it's giving a foreign language construct more weight in the language than it should have. Yeah it's used widely, but so is `hexlit!(...)`, and where do we stop.
|
2 comments
 @thejpster It wasn't, but it could have been even more easily than adding c"" (especially in core that has access to const_eval_select); until then, cstr crate provided it. |
@chrysn was cstr! in libcore?
As someone who has to make Rust talk to things that already exist, I’m happy it’s going in - C is not a language it’s an ABI and it’s an ABI Rust claims to support.