On Monday, 11 August 2014 at 22:59:34 UTC, H. S. Teoh via
Digitalmars-d wrote:
1) Make Wrapper.func() a template function, so that the
deprecation
message is not triggered unless the user actually calls it (in
which
case the deprecation message *should* be triggered). The
problem is that
when the deprecation message *is* triggered, it comes from deep
inside
Phobos, and users may complain, why did you export a
bidirectional range
API if that support is already deprecated?
After some thinking about it I am leaning towards this option
again. If there is some user code that relies on bidirectional
API exposed then it probably should get deprecation warning after
all.
I may change my mind again though :)
