2026/03/04

Newest at the top

2026-03-04 01:42:00 +0100nschoe(~nschoe@2a01:e0a:8e:a190:bcc4:c62f:8a83:eae8) nschoe
2026-03-04 01:41:51 +0100jtnuttall(~jeremy@user/jeremyn) (Ping timeout: 255 seconds)
2026-03-04 01:41:49 +0100 <chromoblob> i mean, parse and execute
2026-03-04 01:41:38 +0100fgarcia(~lei@user/fgarcia) fgarcia
2026-03-04 01:40:31 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2026-03-04 01:38:57 +0100 <chromoblob> geekosaur: if we didn't care about computer reading programs, though, then it couldn't read them :ь
2026-03-04 01:38:14 +0100 <int-e> I guess there's that (the type for the full example won't fit inside an IRC message)
2026-03-04 01:37:43 +0100 <yahb2> \f -> let start c = c []; push z x c = c (x:z); end z = z in (start `asTypeOf` f) push 1 end ; :: Num t => ; (([t] -> t -> ([t] -> [t]) -> [t]) -> t -> ([t] -> [t]) -> [t]) ; -> [t]
2026-03-04 01:37:43 +0100 <int-e> % :t \f -> let start c = c []; push z x c = c (x:z); end z = z in (start `asTypeOf` f) push 1 end
2026-03-04 01:37:06 +0100 <chromoblob> i'm too impatient, though :)
2026-03-04 01:36:40 +0100 <chromoblob> yin: i think a bit of both
2026-03-04 01:35:22 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-03-04 01:34:39 +0100 <chromoblob> i hoped it would print the actual type in the error message lol
2026-03-04 01:34:31 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2026-03-04 01:34:14 +0100 <EvanR> () is not a specialization of ([a] -> b) -> b
2026-03-04 01:34:08 +0100 <chromoblob> i'm silly...
2026-03-04 01:33:53 +0100 <lambdabot> Probable cause: ‘start’ is applied to too few arguments
2026-03-04 01:33:53 +0100 <lambdabot> with actual type ‘([a0] -> t0) -> t0’
2026-03-04 01:33:53 +0100 <lambdabot> Couldn't match expected type ‘()’
2026-03-04 01:33:52 +0100 <chromoblob> > let start c = c []; push z x c = c (x:z); add (x:y:z) c = c (x+y:z); end z = z in (start :: ()) push 1 push 2 push 3 add add end
2026-03-04 01:33:50 +0100nschoe(~nschoe@82-65-202-30.subs.proxad.net) (Ping timeout: 252 seconds)
2026-03-04 01:33:40 +0100 <EvanR> depends if you have monomorphism restriction!
2026-03-04 01:33:36 +0100 <yin> is this an interesting exercise or will i just explore my patience?
2026-03-04 01:33:17 +0100 <chromoblob> no it's not modification, it's a changed copy... :)
2026-03-04 01:32:45 +0100 <EvanR> it was "modified" (specialized) for its use in start push 1 push 2 push 3 add add end
2026-03-04 01:32:44 +0100 <int-e> yin: that's the easy part... but what's the type it's used at in the final expression?
2026-03-04 01:32:40 +0100 <chromoblob> hmmm
2026-03-04 01:32:37 +0100 <lambdabot> [6]
2026-03-04 01:32:36 +0100 <chromoblob> > let start c = c []; push z x c = c (x:z); add (x:y:z) c = c (x+y:z); end z = z in (start :: _) push 1 push 2 push 3 add add end
2026-03-04 01:32:06 +0100 <yin> ([a] -> b) -> b ?
2026-03-04 01:32:00 +0100 <chromoblob> i briefly thought that 'start's type would be modified by sibling definitions
2026-03-04 01:29:28 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn
2026-03-04 01:27:34 +0100 <EvanR> cool I got the type of start in the first try... at least the most general type xD
2026-03-04 01:23:47 +0100 <lambdabot> ()
2026-03-04 01:23:46 +0100 <int-e> @type () -- or this for lambdabot
2026-03-04 01:23:12 +0100 <yahb2> () -- the space is required for yahb2; the : is for ghci :: ()
2026-03-04 01:23:12 +0100 <int-e> % :type () -- the space is required for yahb2; the : is for ghci
2026-03-04 01:22:39 +0100chromoblobtried
2026-03-04 01:22:08 +0100 <chromoblob> %type ()
2026-03-04 01:19:37 +0100 <chromoblob> wow
2026-03-04 01:19:25 +0100 <int-e> yin: if you want to go mildly insane, work out the type of the `start` in there.
2026-03-04 01:18:55 +0100merijn(~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2026-03-04 01:18:37 +0100 <yin> int-e: yay continuations
2026-03-04 01:18:27 +0100 <lambdabot> * says: | shapr remembers that hours of coding can save minutes of thinking
2026-03-04 01:18:27 +0100 <int-e> @quote *
2026-03-04 01:18:11 +0100 <chromoblob> int-e: wow
2026-03-04 01:17:19 +0100 <EvanR> it's like * in C >:D
2026-03-04 01:17:15 +0100 <yin> this is not good
2026-03-04 01:17:01 +0100 <lambdabot> [1,2,3]
2026-03-04 01:17:00 +0100 <yin> > succ` fmap `[0..2]