allowing unqualified method names in instance declarations
The attached patch shall help accepting an instance declaration like
import qualified Custom
instance Custom.Class T where methodA = ... methodB = ...
by translating it to
instance Custom.Class T where Custom.methodA = ... Custom.methodB = ...
I don't know, whether this also works if you do
import qualified Custom hiding (methodA, methodB, )
John recently sent two patches to jhc@haskell.org, that are not present in the darcs repository. Do they need some confirmation? They work for me, as far as I can judge.
Henning Thielemann wrote:
The attached patch shall help accepting an instance declaration like
import qualified Custom
instance Custom.Class T where methodA = ... methodB = ...
by translating it to
instance Custom.Class T where Custom.methodA = ... Custom.methodB = ...
Correct.
I don't know, whether this also works if you do
import qualified Custom hiding (methodA, methodB, )
according to the standard as well as GHC, it would be an error.
On Sat, Nov 14, 2009 at 06:58:11PM +0100, Henning Thielemann wrote:
The attached patch shall help accepting an instance declaration like
import qualified Custom
instance Custom.Class T where methodA = ... methodB = ...
by translating it to
instance Custom.Class T where Custom.methodA = ... Custom.methodB = ...
Cool! Thanks. this fixes a long standing bug.
John recently sent two patches to jhc@haskell.org, that are not present in the darcs repository. Do they need some confirmation? They work for me, as far as I can judge.
I had not pushed them to the web site by accident. they should be there now. If possible, you should use 'darcs send' to send patches to the list so my automation will recognize them as patches and my application scripts will work. Thanks for the patches! John -- John Meacham - ⑆repetae.net⑆john⑈ - http://notanumber.net/
On Sat, 14 Nov 2009, John Meacham wrote:
If possible, you should use 'darcs send' to send patches to the list so my automation will recognize them as patches and my application scripts will work. Thanks for the patches!
I never had the luck to get a darcs where the built-in mail sending worked. Maybe I have to configure or install something in order to get it running?
On Sun, Nov 15, 2009 at 12:16:48AM +0100, Henning Thielemann wrote:
If possible, you should use 'darcs send' to send patches to the list so my automation will recognize them as patches and my application scripts will work. Thanks for the patches!
I never had the luck to get a darcs where the built-in mail sending worked. Maybe I have to configure or install something in order to get it running?
You need a working mail set up on whatever machine you are running 'darcs send' from. for instance, on linux, you may need to install sendmail or my preference, postfix. Depending on your internet connection, you may have to point it at an external mail server if they block the SMTP ports. If this doesn't work for you, you can still send them as attachments, I'll just have to keep an eye out for them. John -- John Meacham - ⑆repetae.net⑆john⑈ - http://notanumber.net/
participants (3)
-
Henning Thielemann -
Isaac Dupree -
John Meacham