On Monday, 8 April 2013 at 09:41:52 UTC, Iain Buclaw wrote:
It uses some type information, eg:
const/immutable/wild -> qualified const.
shared -> qualified volatile.
shared + const/wild -> qualified const/volatile.
const/wild can be muted via aliasing. I'm not sure how GCC's
backend understand const, but this seems unclear to me if this is
correct.
Done nothing in regards to C 'restrict' optimisations. However
the D array
.ptr type could also be considered 'restrict' also.
slices can alias each other. Same as above, is that correct ?
