Re: DeriveFoldable treatment of tuples is surprising

2017-03-22 Thread Sven Panne
2017-03-21 22:29 GMT+01:00 Edward Kmett : > [... In general I think the current behavior is the least surprising as it > "walks all the a's it can" and is the only definition compatible with > further extension with Traversable. [...] > OTOH, the current behavior contradicts my intuition that wra

Re: DeriveFoldable treatment of tuples is surprising

2017-03-22 Thread Oliver Charles
> there is a fair bit of user code for things like vector types that do things like newtype V3 a = V3 (a,a,a,a) ^ 1 2 3 4(!?) Oh boy, I sure hope not ;) On Wed, Mar 22, 2017 at 8:14 AM Sven Panne wrote: > 2017-03-21 22:29 GMT+01:00 Edward Kmett : > > [... In general I think th

Re: DeriveFoldable treatment of tuples is surprising

2017-03-22 Thread Twan van Laarhoven
On 2017-03-21 21:34, David Feuer wrote: This seems much too weird: *> :set -XDeriveFoldable *> data Foo a = Foo ((a,a),a) deriving Foldable *> length ((1,1),1) 1 *> length $ Foo ((1,1),1) 3 This is not unique to tuples, consider: > :set -XDeriveFoldable > data Foo a = Foo [[a]] derivi

WARNING in hptSomeThingsBelowUs

2017-03-22 Thread Ben Franksen
This is what I get after removing a file from the working tree and also from the cabal file for the project and then rebuild. WARNING in hptSomeThingsBelowUs missing module Darcs.Util.Environment Probable cause: out-of-date interface files I am using cabal new-build. Cabal folks tell me this

Re: WARNING in hptSomeThingsBelowUs

2017-03-22 Thread Evan Laforge
I've been seeing this since 6.12. I brought it up 7 (!) years ago, but unfortunately it doesn't look like I filed a bug as Simon requested. I probably failed to reproduce easily, and then forgot. But it still definitely happens. On Wed, Mar 22, 2017 at 3:59 PM, Ben Franksen wrote: > This is wha

Re: WARNING in hptSomeThingsBelowUs

2017-03-22 Thread Ben Franksen
I can provide a test case (the darcs darcs repo) where I have just seen this for the second time. Am 23.03.2017 um 00:43 schrieb Evan Laforge: > I've been seeing this since 6.12. I brought it up 7 (!) years ago, > but unfortunately it doesn't look like I filed a bug as Simon > requested. I proba