<div dir="ltr"><div>I'm ok with acceptance (I recall this idea has come up several times in the past, it's definitely useful sometimes). But I agree with Iavor that the proposal needs some details to be nailed down.</div><div><br></div><div>Cheers</div><div>Simon<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 24 May 2018 at 18:04, Iavor Diatchki <span dir="ltr"><<a href="mailto:iavor.diatchki@gmail.com" target="_blank">iavor.diatchki@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I have a bunch of question about this proposal, but I wrote them on the proposal discussion page, as this is what folks asked for, last time I had some questions. I think answering them would make the proposal more clear. <div><br></div><div>It seems to me that the use of this extension is somewhat limited, but it could be useful on occasion so I could take it or leave it. It's been a while since I've looked at the GHC source, but I don't think that implementing this would be completely trivial, as I don't thing GHC currently cares about *how* names came to in scope, just what they refer to. But, I believe this is usually not a big factor in our discussions, just though I'd mention it.</div><div><br></div><div>-Iavor</div><div><br></div><div><div><div><br></div><div><br></div></div></div></div><br><div class="gmail_quote"><div><div class="h5"><div dir="ltr">On Thu, May 24, 2018 at 3:23 AM Joachim Breitner <<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">Hi,<br>
<br>
alanasp has proposed a Deprecating Exports mechanism:<br>
<a href="https://github.com/alanasp/ghc-proposals/blob/patch-2/proposals/deprecating_exports_proposal.rst" rel="noreferrer" target="_blank">https://github.com/alanasp/<wbr>ghc-proposals/blob/patch-2/<wbr>proposals/deprecating_exports_<wbr>proposal.rst</a><br>
<br>
The gist is explained by this:<br>
<br>
module Data.List<br>
( ...<br>
{-# DEPRECATE lines "Exported from Data.String instead" #-}<br>
, lines<br>
...t<br>
) where<br>
<br>
i.e. DEPRECATE pragmas in export lists cause warning when some other<br>
module uses the deprecated symbol when it is imported (only) via some<br>
deprecated export.<br>
<br>
This is a GSOC 2018 project, mentored by Matthew Pickering and Erik de<br>
Castro Lopo.<br>
<br>
The feature has a clear use-case, is self-contained and David Feuer<br>
(the containers maintainer) has already confirmed that there is a real<br>
demand for this. I suggest acceptance!<br>
<br>
<br>
As always, I will understand silence as tactic consensus.<br>
<br>
Cheers,<br>
Joachim<br>
<br>
<br>
-- <br>
Joachim Breitner<br>
<a href="mailto:mail@joachim-breitner.de" target="_blank">mail@joachim-breitner.de</a><br>
<a href="http://www.joachim-breitner.de/" rel="noreferrer" target="_blank">http://www.joachim-breitner.<wbr>de/</a><br></div></div>
______________________________<wbr>_________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org" target="_blank">ghc-steering-committee@<wbr>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-<wbr>bin/mailman/listinfo/ghc-<wbr>steering-committee</a><br>
</blockquote></div>
<br>______________________________<wbr>_________________<br>
ghc-steering-committee mailing list<br>
<a href="mailto:ghc-steering-committee@haskell.org">ghc-steering-committee@<wbr>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-<wbr>bin/mailman/listinfo/ghc-<wbr>steering-committee</a><br>
<br></blockquote></div><br></div>