Nice!
On 24 May 2014 12:42, Huon Wilson wrote:
> I believe much of the underlying issue is covered by #12808. I have just
> filed a pull request #14402 to "fix" the immediate symptoms of this bug by
> making it harder to accidentally have struct fields taht conflict with the
> private fields o
I believe much of the underlying issue is covered by #12808. I have just
filed a pull request #14402 to "fix" the immediate symptoms of this bug
by making it harder to accidentally have struct fields taht conflict
with the private fields of the libstd types.
There's also issue #13126 and RFC #
No, I was just getting feedback if this was a problem already considered. I
have not been following all Rust progress very closely (trying to catch up
now). But I can try to do so later.
Regards,
Paulo
On 23 May 2014 22:06, Kevin Ballard wrote:
> This looks like a legitimate problem. Have you
This looks like a legitimate problem. Have you filed an issue on the GitHub
issues page? https://github.com/mozilla/rust/issues/new
-Kevin
On May 23, 2014, at 6:04 AM, Paulo Sérgio Almeida wrote:
> Hi all, (resending from different email address; there seems to be a
> problem with my othe
Hi all, (resending from different email address; there seems to be a
problem with my other address)
I don't know if this has been discussed, but I noticed an unpleasant
interaction between private fields in the implementation of things like
pointer types and auto-dereferencing.
The example I
