Re: <.> defined in GHC and System.FilePath

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