<div dir="ltr"><div dir="ltr">On Wed, 21 Oct 2020 at 07:40, Spiwack, Arnaud <<a href="mailto:arnaud.spiwack@tweag.io">arnaud.spiwack@tweag.io</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Simon (Marlow):</div><div><br></div><div>Do I understand correctly that what you are objecting to is the following syntax in the proposal</div><div><br></div><div> module M where</div><div> import module M where</div><div><br></div><div>And would rather have</div><div><br></div><div> qualified module M where</div><div> module M where</div><div><br></div><div>To mimic the import declaration behaviour?<br></div></div></blockquote><div><br></div><div>Yes. And instead of <br></div><div><br></div><div> import M (module N)<br></div><div><div> import M (import module N)</div><div><br></div><div>we would write<br></div><br></div><div><div> import M (qualified module N)<br></div><div><div> import M (module N)</div></div></div><div> </div><div>It seems to me to be desirable to use the same convention for all of:<br></div><div><div> * importing modules at the top level ([import M [qualified])<br></div><div> * importing a local module (import M ([qualified] module N))<br></div> * declaring a local module ([qualified] module M where ..)</div><div> * exporting a local module (module M ([qualified] module M) where)<br></div><div> </div><div>and perhaps it would be a source of confusion if these were different, as in the proposal. (but it's hard to tell, since we don't have any experience with using the extension yet.)<br></div><div><br></div><div>Richard, what do you think?</div><div><br></div><div>Cheers</div><div>Simon</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Oct 17, 2020 at 9:33 PM Alejandro Serrano Mena <<a href="mailto:trupill@gmail.com" target="_blank">trupill@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I like the proposal as it stands.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El jue., 15 oct. 2020 a las 20:09, Spiwack, Arnaud (<<a href="mailto:arnaud.spiwack@tweag.io" target="_blank">arnaud.spiwack@tweag.io</a>>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">In<br>
particular excited about the ability to locally open a module<br>
(something that I began to like when writing Ocaml).<br></blockquote><div><br></div><div>It is also one of my favourite features in Ocaml. It's a fairly recent addition to Ocaml (10ish years ago, I would say?), and I believe it's fair to say that it had a profound impact on coding style throughout the community. For the better in my opinion.<br></div></div></div>
_______________________________________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br>
</blockquote></div>
</blockquote></div>
_______________________________________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@haskell.org</a><br>
<a href="https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee" rel="noreferrer" target="_blank">https://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-steering-committee</a><br>
</blockquote></div></div>