2025/02/12

Newest at the top

2025-02-12 22:33:02 +0100 <geekosaur> whoops, didn;t notice I was beaten to it
2025-02-12 22:33:01 +0100 <merijn> there we go
2025-02-12 22:32:54 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-02-12 22:32:45 +0100 <tomsmeding> ah
2025-02-12 22:32:43 +0100 <tomsmeding> english
2025-02-12 22:32:42 +0100 <lambdabot> cmccann says: you want a debugger? GHC has one. Except that stepping through lazy evaluation is like listening to a stream of consciousness narrative told by a 5-year-old with ADHD.
2025-02-12 22:32:42 +0100 <geekosaur> @quote stream.of.conscious
2025-02-12 22:32:40 +0100 <lambdabot> cmccann says: you want a debugger? GHC has one. Except that stepping through lazy evaluation is like listening to a stream of consciousness narrative told by a 5-year-old with ADHD.
2025-02-12 22:32:40 +0100 <tomsmeding> @quote stream.of.consciou
2025-02-12 22:32:26 +0100 <merijn> really?
2025-02-12 22:32:23 +0100 <merijn> aww
2025-02-12 22:32:21 +0100 <lambdabot> No quotes match. That's something I cannot allow to happen.
2025-02-12 22:32:21 +0100 <merijn> @quote stream.of.concious
2025-02-12 22:31:51 +0100 <EvanR> I will now look up :trace
2025-02-12 22:31:45 +0100target_i(~target_i@user/target-i/x-6023099) (Quit: leaving)
2025-02-12 22:31:38 +0100 <geekosaur> in particular :trace is a thing
2025-02-12 22:31:31 +0100 <monochrom> I sympathize with wanting a stepper. But at this stage it looks like you haven't even grokked type inference and instance resolution.
2025-02-12 22:31:12 +0100 <EvanR> I write :t something in ghci and see if it 1. works and 2. corresponds with my expectations. It helped
2025-02-12 22:31:11 +0100 <merijn> (that is, not affecting build artifacts)
2025-02-12 22:31:03 +0100 <merijn> monochrom: so they do, but I'm protecting you and or screwing you (choose as appropriate) by deleting any of your flags I deemed dumb :p
2025-02-12 22:31:02 +0100 <tomsmeding> well it's still correct, but now non-sarcastically
2025-02-12 22:30:54 +0100 <tomsmeding> oh you added "un"
2025-02-12 22:30:41 +0100tomsmedingnods vigorously
2025-02-12 22:30:34 +0100 <tomsmeding> very
2025-02-12 22:30:29 +0100 <EvanR> seems to be wildly unpopular
2025-02-12 22:30:19 +0100 <EvanR> justsomeguy, ghci has a debugger
2025-02-12 22:30:19 +0100tri(~tri@ool-44c70bcb.dyn.optonline.net)
2025-02-12 22:30:10 +0100 <merijn> monochrom: only the ones I don't explicit remove from you behind your back :p
2025-02-12 22:29:41 +0100 <monochrom> I thought flags went into the hash and can trigger rebuild.
2025-02-12 22:29:03 +0100 <merijn> still open, sadly, because it was never enough of a problem to invent a solution
2025-02-12 22:28:46 +0100tanky(sid630849@user/tanky) tanky
2025-02-12 22:28:46 +0100tanky(sid630849@id-630849.tinside.irccloud.com) (Changing host)
2025-02-12 22:28:22 +0100 <tomsmeding> merijn: <3
2025-02-12 22:28:11 +0100 <tomsmeding> justsomeguy: you'll get two different results for the outer and the inner fmap
2025-02-12 22:28:04 +0100 <merijn> tomsmeding: https://github.com/haskell/cabal/issues/5300
2025-02-12 22:28:02 +0100 <merijn> tomsmeding: I'm ahead of you by 7 years :)
2025-02-12 22:27:59 +0100 <tomsmeding> justsomeguy: write down the type of `fmap`; write down the types of the arguments it gets in your expression; match the two and see what the `f` in fmap's type should be
2025-02-12 22:27:46 +0100 <EvanR> I reversed the arguments, nevermind me
2025-02-12 22:27:26 +0100tanky(sid630849@id-630849.tinside.irccloud.com)
2025-02-12 22:26:50 +0100 <EvanR> (fmap (fmap sum) Just) [1,2,3] => (Just . fmap sum) [1,2,3]
2025-02-12 22:26:48 +0100yegorc(~yegorc@user/yegorc) (Leaving)
2025-02-12 22:26:47 +0100 <tomsmeding> merijn: I do wonder if just dropping those flags is the right design though; sure, perhaps the user didn't intend to recompile the world, but perhaps they did!
2025-02-12 22:26:45 +0100 <monochrom> More than that, you need a tool that tells you what "fmap" resolves to.
2025-02-12 22:26:43 +0100biberu(~biberu@user/biberu) biberu
2025-02-12 22:26:38 +0100 <merijn> tomsmeding: Yes, because cabal-install just invokes the Setup.hs parser
2025-02-12 22:26:32 +0100 <justsomeguy> Maybe a haskell debugger?
2025-02-12 22:26:12 +0100 <justsomeguy> Is there some tool I can put this into and see the evaluation process step-by-step?
2025-02-12 22:25:21 +0100 <euouae> I misreead it, so (->) on JUst
2025-02-12 22:25:14 +0100tabaqui1(~root@87.200.129.102) (Ping timeout: 252 seconds)
2025-02-12 22:25:09 +0100 <EvanR> f x y z = ((f x) y) z