Bug 14780 – Non-intuitive behavior for pointers to aggregates defining opSlice

``` struct HasOpSlice { int opSlice() { return 10; } } void main() { HasOpSlice* pointer; int i = pointer[]; } ``` test.d(9): Error: need upper and lower bound to slice pointer I'd like for this to Just Work(tm). I don't have any good ideas for how to make this behave consistently in the case that there's an opSlice that takes two arguments.

Currently, operator overloads don't go through pointers. I.e., this isn't unique to opSlice. Only letting opSlice go through pointers would be silly, in my opinion. Doing it for all operators would be quite a change and should be well thought out.

Yeah, this definitely isn't valid. You need a wrapper around the pointer to properly forward.