On Friday, 25 November 2016 at 15:46:15 UTC, Steven Schveighoffer
wrote:
This case you have of defining a popFront member variable with
opCall -- don't do that, it will break things (I'm sure there
are already many places where popFront is called without
parens). I don't think that's a case that we need worry about.
Seems like not that many.
grep -r "popFront;" *
algorithm/comparison.d: r2.popFront;
algorithm/comparison.d: r1.popFront;
algorithm/comparison.d: r1.popFront;
algorithm/comparison.d: r2.popFront;
algorithm/mutation.d: void popFront() { data.popFront; }
experimental/allocator/typed.d: front, popFront;
experimental/ndslice/selection.d:
val.popFront;
experimental/ndslice/selection.d: elems2.popFront;
experimental/ndslice/selection.d: elems2.popFront;
experimental/ndslice/selection.d: elems.popFront;
experimental/ndslice/slice.d: slice.popFront;
experimental/ndslice/slice.d: slice.popFront;
experimental/ndslice/slice.d: value.popFront;
experimental/ndslice/slice.d: slice.popFront;
experimental/ndslice/slice.d: value.popFront;
experimental/ndslice/slice.d: slice.popFront;
experimental/ndslice/slice.d: slice.popFront;
experimental/ndslice/slice.d: slice.popFront;
experimental/ndslice/slice.d: slice.popFront;
experimental/ndslice/slice.d: slice.popFront;
experimental/ndslice/slice.d: slice.popFront;
range/package.d: return condition ? r1.popFront :
r2.popFront;
The last one is strange.
