indeed .. and we can reasonably say "lets deal with the bandaid in one go by cleaning it up in the next standard"
so what would the next gen look like? eg: fresh variables get the usual implicit forall at the front of the type, and everything else either needs an explicit quantifier OR it refers to the outer implicit quantified variable? On Sat, May 19, 2018 at 2:56 PM, Brandon Allbery <allber...@gmail.com> wrote: > On Sat, May 19, 2018 at 7:32 AM, Anthony Clayden < > anthony_clay...@clear.net.nz> wrote: > >> So the explanation I've seen for the current design is it was deliberately >> idiosyncratic, to minimise any disruption to existing code. Then I'm asking >> whether any of that code is still around? If not/if it's been re-factored to >> use ScopedTypeVariables, then any tweak to the design could have a freer >> hand. >> >> > The reason there's no discussion about that is that nobody here has the > ability to go hunt down every last piece of code in every public or private > (think Standard Chartered, Facebook, etc.) code base and its current owner, > and order them to "fix" it. You can't win that battle. > > -- > brandon s allbery kf8nh sine nomine > associates > allber...@gmail.com > ballb...@sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad > http://sinenomine.net > > _______________________________________________ > Glasgow-haskell-users mailing list > Glasgow-haskell-users@haskell.org > http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users > >
_______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/glasgow-haskell-users
