<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">On the first point , I suggest we propose it in the thread and see what the author has to say.<div class=""><br class=""></div><div class="">On the second point I am all in favour of splitting out <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">-XNamespacedImport.</span></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class=""></span></font></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">Chris</span></font></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class=""></span></font><div><br class=""><blockquote type="cite" class=""><div class="">On 7 Dec 2022, at 18:12, Joachim Breitner <<a href="mailto:mail@joachim-breitner.de" class="">mail@joachim-breitner.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi,<br class=""><br class="">generally in favor; these new warnings shoudn’t do harm and are<br class="">hopefully useful to some.<br class=""><br class="">But I have a technical issue (sorry for being so late with that):<br class=""><br class="">I note that this proposal extends -XExplicitNamespaces, which so far<br class="">can be used to distinguish type from term operators in export and<br class="">import lists, by allowing them to be prefixed with `type` (but not<br class="">`data`!), as in: import N( f, type (++) )<br class=""><a href="https://downloads.haskell.org/ghc/latest/docs/users_guide/exts/explicit_namespaces.html" class="">https://downloads.haskell.org/ghc/latest/docs/users_guide/exts/explicit_namespaces.html</a><br class=""><br class="">The new extension now extends this extension the<br class=""><br class=""> import qualified Foo data as FD<br class=""> import qualified Foo type as FT<br class=""><br class="">forms to “filter” imports by namespace. A few points:<br class=""><br class="">* It seems to be inconsistent to allow both `type` and `data` in the <br class=""> filtered-import, but as a qualifier on individual only `type`. Should<br class=""> we allow the use of `data` in import/export lists as well?<br class=""><br class=""> import N(f, type (++), data (+))<br class=""><br class="">* As discussed in<br class=""> https://github.com/ghc-proposals/ghc-proposals/issues/551,<br class=""> -XExplicitNamespaces, which is quite old and is implied by <br class=""> -XTypeOperators which is implied by -XGHC2021 probably ought to have<br class=""> been in GHC2021 as well, and I’d like to include it in GHC2023 (if <br class=""> that exists) to fix that (see #559). But that feels inappropriate<br class=""> if we extend that extension in this way.<br class=""><br class="">We could side-step that issue if we put he new forms in their own<br class="">language extension (maybe -XNamespacedImport)? WDYT?<br class=""><br class="">Cheers,<br class="">Joachim<br class="">-- <br class="">Joachim Breitner<br class=""> mail@joachim-breitner.de<br class=""> http://www.joachim-breitner.de/<br class=""><br class="">_______________________________________________<br class="">ghc-steering-committee mailing list<br class="">ghc-steering-committee@haskell.org<br class="">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee<br class=""></div></div></blockquote></div><br class=""></div></body></html>