Allow top-level shadowing for imported names?

Carter Schonwald carter.schonwald at gmail.com
Wed Oct 5 13:20:45 UTC 2016


Yeah... let's not have import order sensitivity.

On Wednesday, October 5, 2016, Yitzchak Gale <gale at sefer.org> wrote:

> Yuras Shumovich wrote:
> >> Can we generalize the proposal such that subsequent imports shadow
> >> preceding ones?
>
> Herbert Valerio Riedel wrote:
> > ...iirc there is a different idea...
> > allowing explicitly enumerated names...
> > to shadow imports from other modules which didn't explicitly name the
> > same import; effectively introducing a higher-priority scope for names
> > imported explicitly.
>
> Conversely - the original proposal should be modified to remain
> an error, not a warning, when the symbol was imported explicitly
> on an import list and then redefined locally at the top level.
> This is equivalent to defining a symbol twice in the same scope.
>
> Thanks,
> Yitz
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org <javascript:;>
> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/ghc-devs/attachments/20161005/d52d5f9c/attachment.html>


More information about the ghc-devs mailing list