http://d.puremagic.com/issues/show_bug.cgi?id=2584



--- Comment #8 from Iain Buclaw <ibuc...@ubuntu.com> 2012-10-10 03:32:04 PDT ---
(In reply to comment #7)
> (In reply to comment #6)
> > Note:
> > 
> > The D2-way of doing this is by using shared.
> 
> Really? I thought it was nothing more than a type-safety marker. So shared
> actually makes a variable volatile?

Not the variable, but it's type is qualified as volatile, this produces subtly
different codegen (IIRC volatile on the var would mean it is loaded thrice
also). Given it's use in atomics, and that data-depending ordering is
essential. I felt this to be important.  Similarly for immutable, which sets
the type as being const qualified.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------

Reply via email to