News for hackers. Stuff that matters.

A comment on Announcing Rust 1.30. Parent comment

Re:Announcing Rust 1.30 by steveklabnik on Thursday October 25, 2018 @01:31PM (#18302664)
I read the parent as suggesting that you could call it as

  _async(true)
[ Parent | on HN ]
Re:Announcing Rust 1.30 by weberc2 on Thursday October 25, 2018 @02:48PM (#18303461)
No, this isn't what I meant to imply (though I understand your confusion). I didn't realize (or understand) that the syntax is meant to facilitate interoperability between different versions of Rust.
[ Parent | on HN ]
Re:Announcing Rust 1.30 by shepmaster on Thursday October 25, 2018 @01:35PM (#18302713)
Ah. If that's the case, as you point out people might have already been using a leading underscore (although they shouldn't for idiomatic reasons), leading to ambiguity around

2015 code:

     fn async(enabled: bool) {}
     fn _async(enabled: bool) {}
2018 code calling that:

    _async(true); // Which is this calling?
[ Parent | on HN ]