On Sunday, 3 January 2016 at 17:25:40 UTC, tsbockman wrote:
On Sunday, 3 January 2016 at 17:18:05 UTC, Jakob Ovrum wrote:
Yes, but it shouldn't be designed around a bug.
Unless the bug is actually going to be fixed some time soon,
why would I deliberately design something in a way that is
broken? Does it really matter *why* it is broken?
So, we're talking about a library using CheckedInt. If the
library selectively imports anything from CheckedInt at
module-level, it'll always be public due to a bug.
This is trivial to work around. Often the import can be nested,
and when it can't, a static import or renamed module import can
be used to resolve conflicts.
It's not a big deal.
