On 10/26/15 12:27 PM, Dmitry Olshansky wrote:
Agreed. That is my opinion as well, however luck of any attention from
you and Walter led to the point where we
need (a) and (b) to work right now and we hacked it (somewhat of
speaking for the community here, correct me if I'm wrong).
I agree we need to make progress but that's a bit of a tautology and
requires judgment on what is progress etc.
FWIW this is one of those cases in which short-term progress may hurt
long-term progress. Again: tactical prowess, no matter how impressive,
should not be a substitute for strategy.
Release is unavoidable. Let us ship it then figure out the optimal
string like definition. The whole auto-decoding mess together with alias
this mess is important to solve but must not prevent us from releasing
on time.
If we release now, we're stuck with isStringLike forever. Any chance
of at least making it package?
I believed it was private/package hack. Anyhow we can redefine how
isStringLike exactly works as long as semantics stay sane.
I see isStringLike is public and documented. At the very least we need
to make it undocumented.
Andrei
_______________________________________________
phobos mailing list
[email protected]
http://lists.puremagic.com/mailman/listinfo/phobos
