2025/08/03

Newest at the top

2025-08-03 23:39:18 +0200qqe(~qqq@185.54.20.59)
2025-08-03 23:37:52 +0200califax(~califax@user/califx) califx
2025-08-03 23:37:37 +0200califax(~califax@user/califx) (Ping timeout: 240 seconds)
2025-08-03 23:30:02 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-08-03 23:26:41 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 248 seconds)
2025-08-03 23:25:23 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-08-03 23:24:07 +0200caubert(~caubert@user/caubert) (Ping timeout: 276 seconds)
2025-08-03 23:24:01 +0200jmorris(uid604645@id-604645.hampstead.irccloud.com) jmorris
2025-08-03 23:20:54 +0200amadaluzia(~amadaluzi@user/amadaluzia) amadaluzia
2025-08-03 23:17:13 +0200caubert(~caubert@user/caubert) caubert
2025-08-03 23:14:54 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-08-03 23:07:40 +0200pavonia(~user@user/siracusa) siracusa
2025-08-03 23:06:03 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-08-03 23:04:09 +0200 <yin> ^would include polymorphic map yes please thank you
2025-08-03 23:02:58 +0200caubert(~caubert@user/caubert) (Ping timeout: 272 seconds)
2025-08-03 23:02:19 +0200trickard_(~trickard@cpe-56-98-47-163.wireline.com.au)
2025-08-03 23:02:11 +0200 <yin> -XNoTrainingWheels
2025-08-03 23:02:09 +0200jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 248 seconds)
2025-08-03 23:02:05 +0200trickard(~trickard@cpe-56-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-08-03 22:58:09 +0200 <monochrom> If you do so much as entering `[]` or `print []` at the REPL, people freak out with "OMG why is it an ambiguity error for such a trivial case why can't it just print out "[]" why can't the computer just DWIM???!!!"
2025-08-03 22:57:56 +0200werneta(~werneta@syn-071-083-160-242.res.spectrum.com) werneta
2025-08-03 22:56:41 +0200 <yin> monochrom: heh
2025-08-03 22:56:28 +0200 <monochrom> It is considered more "user-friendly" if REPL behaviour deviates from production code behaviour. >:)
2025-08-03 22:56:06 +0200 <yin> ah, i have `:seti -Wno-type-defaults` on my .ghci so i didn't even get the warning. with the warning it makes more sense
2025-08-03 22:56:05 +0200 <c_wraith> With the extension, they just defaulted to Integer and things worked.
2025-08-03 22:55:29 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-08-03 22:55:26 +0200 <c_wraith> Heck, I've even used -XExtendedDefaultRules in a module that included a lot of tests of polymorphic functions being passed literals. Because there were constraints aside from the few specified on the types of the literals, every single one would have required a type annotation without the extension
2025-08-03 22:54:16 +0200 <c_wraith> I find the occasional confusion a lot better than all the extra typing to add explicit annotations would be. Mostly because it happens like one a year, but I enter expressions in ghci a lot more frequently.
2025-08-03 22:52:28 +0200 <c_wraith> occasionally it's confusing, but most of the time it's what you wanted anyway
2025-08-03 22:52:10 +0200 <c_wraith> It's about making ghci do *something* without explicit type annotations in a lot more cases.
2025-08-03 22:51:46 +0200caubert(~caubert@user/caubert) caubert
2025-08-03 22:51:13 +0200 <yin> is there a reason?
2025-08-03 22:50:44 +0200 <yin> why is this so inconsistent with standard module loading?
2025-08-03 22:50:42 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-08-03 22:48:09 +0200 <c_wraith> oh no. I am too slow.
2025-08-03 22:47:43 +0200 <mauke> jinx
2025-08-03 22:47:32 +0200 <c_wraith> https://downloads.haskell.org/ghc/latest/docs/users_guide/ghci.html#extension-ExtendedDefaultRules If you want to see what the docs have to say
2025-08-03 22:47:32 +0200 <mauke> https://downloads.haskell.org/ghc/latest/docs/users_guide/ghci.html#type-defaulting-in-ghci
2025-08-03 22:45:59 +0200 <yin> weird
2025-08-03 22:45:43 +0200 <c_wraith> ghci has extra defaulting rules to pin types down
2025-08-03 22:45:33 +0200machinedgod(~machinedg@d75-159-126-101.abhsia.telus.net) (Ping timeout: 244 seconds)
2025-08-03 22:45:17 +0200 <yin> why does ghci accept it if you write it manually but not when :l ?
2025-08-03 22:44:48 +0200 <lambdabot> ‘a0’ arising from a use of ‘show_M68719521878...
2025-08-03 22:44:48 +0200 <lambdabot> • Ambiguous type variables ‘f0’,
2025-08-03 22:44:48 +0200 <lambdabot> error:
2025-08-03 22:44:46 +0200 <mauke> > map pure []
2025-08-03 22:44:43 +0200 <lambdabot> Applicative f => [f a]
2025-08-03 22:44:42 +0200 <mauke> :t map pure []
2025-08-03 22:44:41 +0200mikess(~sam@user/mikess) (Quit: leaving)
2025-08-03 22:44:18 +0200 <yin> oh weird