News for hackers. Stuff that matters.
Re:Async-await on stable Rust by esotericn on Thursday November 07, 2019 @01:25PM (#21475812)
The latter case should be impossible if the method is private?
Re:Async-await on stable Rust by saghm on Thursday November 07, 2019 @09:49PM (#21479601)
In Rust, privacy isn't enforced like that. Private just means that things outside the module can't access them. There's no concept of privacy at the instance level.
Re:Async-await on stable Rust by esotericn on Friday November 08, 2019 @05:37AM (#21481157)
Yes. So don't make any methods that could potentially be passed incorrect arguments public.
Re:Async-await on stable Rust by saghm on Friday November 08, 2019 @11:46AM (#21483974)
That still doesn't preclude the possibility that within the module the function gets called with a field from another instance. I think the idea is that by making it a method that just takes a reference to self, it's impossible to accidentally mutate a field on a different instance, while taking a reference to the field itself doesn't prevent the programmer from accidentally calling it with the wrong instance of the field.