Walter Bright, el 19 de agosto a las 13:08 me escribiste:
> Leandro Lucarella wrote:
> >With the precise heap scanning patch for DMD the GC can automatically
> >pin memory, because it has enough information to differentiate between
> >real pointers and words which types are not really known, so a b
Leandro Lucarella wrote:
With the precise heap scanning patch for DMD the GC can automatically
pin memory, because it has enough information to differentiate between
real pointers and words which types are not really known, so a block can
be moved *only* if is only pointed to by real pointers, ot
Jordi wrote:
But even if "this" is a reference like Lars pointed out, the
method should return a copy of the struct by value, right?
Yes.
Walter Bright, el 18 de agosto a las 15:31 me escribiste:
> bearophile wrote:
> >Walter Bright:
> >
> >>There is no need for a pin attribute, the gc can determine if a class needs
> >> pinning or not.
> >
> >The same is probably true for pure functions too, the compiler can determine
> >what functi
Walter Bright, el 18 de agosto a las 12:25 me escribiste:
> Leandro Lucarella wrote:
> >Walter Bright, el 18 de agosto a las 10:08 me escribiste:
> >>bearophile wrote:
> >>>Currently in the D2 GC there is no notion of pinned/unpinned class
> >>>instances,
> >>>but eventually an attribute as @pinne
On 08/17/2010 02:35 AM, Walter Bright wrote:
Jordi wrote:
Found it. It took me 7 iterations of binary search across the svn
repositories for dmd, druntime and phobos. The commit causing the
issue is 505 in dmd. It is related to structs returning *this, which
indeed i do in my maths structs.
Now
> In the meantime that Reddit thread is one of the worst I've seen on that
> usually interesting site. Some C++ programmers seem to hate D a lot.
In my experience, convincing someone who have personally invested a lot in C++
is _hard_. People who care about big teams are not convinced at all by