opApply and const

[Bill Baxter]

Daniel Keep wrote:
> My apologies.  It *does* actually support arbitrary opApply()s.  What
> probably *doesn't* support are types with more than one opApply.  Can we
> get a list of overloads with D 2.0 yet?

I like it (no surprise since I also like Python).
How about reverse?  Can you cook up a reversed() template that would use 
an opApplyReverse if it exists or else forward iterate into a buffer and 
reverse iterate over that?  Or maybe creating a big temp buffer silently 
isn't such a hot idea...