containers-0.5.6.0 causes GHC testsuite tests to hang about containers HOT 13 CLOSED

I will investigate tomorrow. Also, I will have 0.5.6.1, which in addition to this will fix some warnings I forgot and renames the Typeable.h file, which sometimes aliases with the Typeable.h from base (and generates warnings).

BTW, I am seeing several 'redundant imports' warnings on GHC-head, for example for Applicative(..) from Control.Applicative. I imagine lot of code has to deal with this -- is there a simple way of quieting those warnings while keeping the rest? I could only come up with conditional compilation.

from containers.

I'm pretty sure conditional compilation is the only way. The hangs are a nasty surprise, but I don't know if I'll have a chance to investigate them tonight.

from containers.

On the same subject, the map/coerce tests I added must only be run when optimization is enabled, and I forgot to even think about that. Also, I don't know how. However, that shouldn't lead to any <<<loop>>> exceptions.

from containers.

Why are there tests that only work with optimizations enabled?

As for the imports, we should use conditional compilation.

from containers.

I have disabled the coercion tests for the time being. They depend on RULES being fired, that it why optimization is needed.

from containers.

@hvr I am seeing the problem, my stupid fault which manifests only on base 4.8. That is what I get for not using cabal when testing (as then it does not use MIN_VERSION_base). If you want some laugh, look at toList definition in Foldable class for base 4.8 :-)

I will commit today, after I will perform GHC validation.

from containers.

Once fixed can you please make a bugfix release?

from containers.

I was counting with that, now that I have the rights :-)

from containers.

fyi, I've just added a base < 4.8 constraint to containers-0.5.6.0 to mark that release uninstallable for base-4.8:

http://hackage.haskell.org/package/containers-0.5.6.0/revisions/

from containers.

Thanks, useful.

from containers.

@hvr I just released containers-0.5.6.1. The containers testsuite works on ghc 7-{0,4,6,8,head} and I also validated current ghc-master (only package01e.stderr must be updated to accomodate increased containers version).

from containers.

Why are there tests that only work with optimizations enabled?

Because they are intended to test whether map/coerce RULES are working
properly.

from containers.

@foxik thanks; I updated GHC via ghc/ghc@5444560 yesterday (so today's PPA ghc-head build does already carry containers-0.5.6.1)

from containers.