<.> defined in GHC and System.FilePath

Hi The GHC API uses the <.> operator, which clashes with System.FilePath. Possibly this might want renaming to something else - I have absolutely no idea what it does! Prelude> :m GHC Prelude GHC> :i <.> (<.>) :: HsWrapper -> HsWrapper -> HsWrapper -- Defined in HsBinds Thanks Neil

Neil Mitchell wrote:
The GHC API uses the <.> operator, which clashes with System.FilePath. Possibly this might want renaming to something else - I have absolutely no idea what it does!
Prelude> :m GHC Prelude GHC> :i <.> (<.>) :: HsWrapper -> HsWrapper -> HsWrapper -- Defined in HsBinds
I tend to use import qualified GHC import GHC (Name, Id, ...) i.e. qualify most things, but selectively import a few things unqualified. The GHC API is quite huge, I expect clashes to be fairly common if you import it unqualified. Cheers, Simon

I've no objection to renaming it, if that's more convenient. It's a kind of composition operator, hence the name. Perhaps <:>? By all means send, or commit, a patch Simon | -----Original Message----- | From: glasgow-haskell-users-bounces@haskell.org [mailto:glasgow-haskell-users-bounces@haskell.org] On Behalf Of | Neil Mitchell | Sent: 31 December 2007 15:15 | To: GHC Users | Subject: <.> defined in GHC and System.FilePath | | Hi | | The GHC API uses the <.> operator, which clashes with System.FilePath. | Possibly this might want renaming to something else - I have | absolutely no idea what it does! | | Prelude> :m GHC | Prelude GHC> :i <.> | (<.>) :: HsWrapper -> HsWrapper -> HsWrapper -- Defined in HsBinds | | Thanks | | Neil | _______________________________________________ | Glasgow-haskell-users mailing list | Glasgow-haskell-users@haskell.org | http://www.haskell.org/mailman/listinfo/glasgow-haskell-users

Hi
Simon Marlow wrote: i.e. qualify most things, but selectively import a few things unqualified. The GHC API is quite huge, I expect clashes to be fairly common if you import it unqualified.
On 1/3/08, Simon Peyton-Jones
wrote: I've no objection to renaming it, if that's more convenient. It's a kind of composition operator, hence the name. Perhaps <:>? By all means send, or commit, a patch
If the API is intended to be huge and imported qualified, it doesn't matter if there are clashes. It is trivial to use hiding to solve this, so leaving it alone is fine. Thanks Neil
participants (3)
-
Neil Mitchell
-
Simon Marlow
-
Simon Peyton-Jones