On 26 Oct 2015, at 18:35, Andrei Alexandrescu via phobos wrote:
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.
I've not really been following this discussion, so please disregard the
comment if it does not make sense, but: Wouldn't "isStringLike" appear
in template constraints? If so, then not documenting it is bound to
create even more confusion.
— David
_______________________________________________
phobos mailing list
phobos@puremagic.com
http://lists.puremagic.com/mailman/listinfo/phobos
