Why we need opApply (Was: Can we drop static struct initializers?)

[Walter Bright]

dsimcha wrote:
> If anyone sees any harm in keeping opApply other than a slightly larger language
> spec, please let me know.  Despite its having been superseded by ranges for a
> subset of use cases (and this subset, I will acknowledge, is better handled by
> ranges), I actually think the flexibility it gives in terms of how foreach can be
> implemented makes it one of D's best features.

Thanks for writing this. It's nice to have a compelling argument, and 
you gave one. Looks like opApply is staying.