On 2015-09-28 at 04:56:13 +0200, David Feuer wrote:
[...]
> That's an excellent idea, and I think it makes sense to offer it at the
> module level as well as the class level. Just change DEPRECATED to REMOVED
> when it's actually removed. Speaking of such, has the deprecated export
> proposal mad
It seems like we lost the code that -fwarn-hi-shadow switched during the
add of hierarchical modules in 5.0. And while the hierarchical system makes
the common way .hi files could get shadowed impossible, you can still get
.hi file shadowing if you use the -i flag on multiple folders.
Do we care?
