Re: Unused import warning on re-export

2017-05-15 Thread Iavor Diatchki
ir point. Yes, file a ticket. Better still, offer a patch :-). >> >> Simon >> >> | -Original Message- >> | From: Glasgow-haskell-users [mailto:glasgow-haskell-users- >> | boun...@haskell.org] On Behalf Of Yitzchak Gale >> | Sent: 10 May 2017 13:56

Re: Unused import warning on re-export

2017-05-12 Thread Iavor Diatchki
gow-haskell-users [mailto:glasgow-haskell-users- > | boun...@haskell.org] On Behalf Of Yitzchak Gale > | Sent: 10 May 2017 13:56 > | To: GHC users > | Subject: Unused import warning on re-export > | > | I have a module A with no export list, and a function f which from the > |

RE: Unused import warning on re-export

2017-05-11 Thread Simon Peyton Jones via Glasgow-haskell-users
--Original Message- | From: Glasgow-haskell-users [mailto:glasgow-haskell-users- | boun...@haskell.org] On Behalf Of Yitzchak Gale | Sent: 10 May 2017 13:56 | To: GHC users | Subject: Unused import warning on re-export | | I have a module A with no export list, and a function f which from the |

Unused import warning on re-export

2017-05-10 Thread Yitzchak Gale
I have a module A with no export list, and a function f which from the API point of view should part of the export list of A. But f must be defined in module B, not module A, due an import cycle. I added this line in module A to re-export f from A: import B as A (f) This resulted in an unused imp