Newest at the top
| 2025-02-12 23:08:51 +0100 | <monochrom> | Why is it always traverse? |
| 2025-02-12 23:08:15 +0100 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2025-02-12 23:07:50 +0100 | <merijn> | the other heathens still need to accept our lord and saviour |
| 2025-02-12 23:07:43 +0100 | <tomsmeding> | (: |
| 2025-02-12 23:07:32 +0100 | <merijn> | I have converted at least one colleague to the one true faith of traverse |
| 2025-02-12 23:07:15 +0100 | <tomsmeding> | ah |
| 2025-02-12 23:07:11 +0100 | <merijn> | tomsmeding: it's always traverse |
| 2025-02-12 23:07:09 +0100 | gmg | (~user@user/gehmehgeh) gehmehgeh |
| 2025-02-12 23:06:59 +0100 | <tomsmeding> | merijn: what is? |
| 2025-02-12 23:06:42 +0100 | <merijn> | tomsmeding: Funnily enough still true in scala, although not always as easily implemented :p |
| 2025-02-12 23:06:21 +0100 | gmg | (~user@user/gehmehgeh) (Client Quit) |
| 2025-02-12 23:04:40 +0100 | gmg | (~user@user/gehmehgeh) gehmehgeh |
| 2025-02-12 23:04:22 +0100 | <monochrom> | Interesting. |
| 2025-02-12 23:03:29 +0100 | <tomsmeding> | "it's always `traverse`"? |
| 2025-02-12 23:03:21 +0100 | <tomsmeding> | what even is this ordering, why is it alphabetically ordered except that Traversable is first |
| 2025-02-12 23:02:33 +0100 | finsternis | (~X@23.226.237.192) finsternis |
| 2025-02-12 23:02:30 +0100 | <yahb2> | Traversable Applicative Bounded Enum Eq Floating Foldable Fractional Functor Integral Monad Monoid Num Ord Read RealFloat RealFrac Real Semigroup Show ; ExitSuccess |
| 2025-02-12 23:02:30 +0100 | <tomsmeding> | % System.Process.system "ghci -e ':i Data.Functor.Identity.Identity' | grep '^instance' | cut -d' ' -f2 | xargs" |
| 2025-02-12 23:00:50 +0100 | <tomsmeding> | for better or for worse |
| 2025-02-12 23:00:48 +0100 | gmg | (~user@user/gehmehgeh) (Ping timeout: 264 seconds) |
| 2025-02-12 23:00:45 +0100 | <tomsmeding> | Identity implements a lot of type classes! |
| 2025-02-12 23:00:34 +0100 | <monochrom> | fancy |
| 2025-02-12 23:00:29 +0100 | <lambdabot> | Identity 5 |
| 2025-02-12 23:00:27 +0100 | <monochrom> | > Identity 2 + 3 |
| 2025-02-12 23:00:01 +0100 | <tomsmeding> | ah or Identity, yes |
| 2025-02-12 22:59:32 +0100 | <merijn> | did lambdabot lose his evil instances? |
| 2025-02-12 22:59:26 +0100 | <euouae> | You can do :: Identity Int |
| 2025-02-12 22:59:24 +0100 | <yahb2> | Sum {getSum = 3} |
| 2025-02-12 22:59:24 +0100 | <tomsmeding> | % fmap (+1) (2 :: Data.Monoid.Sum Int) |
| 2025-02-12 22:59:21 +0100 | <lambdabot> | from the context: (Num t, Num t1, Num (t1 -> t)) |
| 2025-02-12 22:59:21 +0100 | <lambdabot> | • Could not deduce (Num t0) |
| 2025-02-12 22:59:21 +0100 | <lambdabot> | error: |
| 2025-02-12 22:59:19 +0100 | <merijn> | > fmap (+1) 2 3 |
| 2025-02-12 22:59:15 +0100 | <merijn> | aww |
| 2025-02-12 22:59:12 +0100 | <lambdabot> | prevents the constraint ‘(Show (f0 Integer))’ from being solved. |
| 2025-02-12 22:59:12 +0100 | <lambdabot> | • Ambiguous type variable ‘f0’ arising from a use of ‘show_M207628434199... |
| 2025-02-12 22:59:12 +0100 | <lambdabot> | error: |
| 2025-02-12 22:59:11 +0100 | <merijn> | > fmap (+1) 2 |
| 2025-02-12 22:59:07 +0100 | remedan | (~remedan@ip-62-245-108-153.bb.vodafone.cz) remedan |
| 2025-02-12 22:58:54 +0100 | <merijn> | monochrom: I mean, is it? :p |
| 2025-02-12 22:58:39 +0100 | remedan_ | (~remedan@ip-62-245-108-153.bb.vodafone.cz) (Ping timeout: 260 seconds) |
| 2025-02-12 22:58:27 +0100 | <monochrom> | Wait, is fmap (+1) 2 supposed to type-check? |
| 2025-02-12 22:56:30 +0100 | <monochrom> | Or worse, you chose the wrong fmap definition, then you rationalized it by misinterpreting the rest of the expression. |
| 2025-02-12 22:56:13 +0100 | <euouae> | justsomeguy: try this instead: `fmap (+1) 2` first |
| 2025-02-12 22:56:12 +0100 | <tomsmeding> | so the "quotes" is indeed accurate, it seems |
| 2025-02-12 22:56:02 +0100 | <tomsmeding> | euouae: experimentally, --ghc-options parses " but passes ' on unchanged |
| 2025-02-12 22:55:33 +0100 | <tomsmeding> | justsomeguy: the order shouldn't matter, which fmap resolves to which definition is determined solely by the types |
| 2025-02-12 22:55:24 +0100 | <monochrom> | You were using the wrong fmap definition. |
| 2025-02-12 22:54:54 +0100 | <justsomeguy> | I'm still confused. Maybe I way trying to apply the outer fmap first, instead of the inner fmap? Figuring out where I went wrong is going to bother me for a while. |
| 2025-02-12 22:54:13 +0100 | <euouae> | tomsmeding: I would say the rest is good, just hold off on the -options variant until more clarification is available |