2024/04/28

Newest at the top

2024-04-28 13:13:59 +0200 <ncf> https://i.imgflip.com/8oapr0.jpg
2024-04-28 13:13:48 +0200paotsaq(~paotsaq@127.209.37.188.rev.vodafone.pt) (Quit: ZNC 1.9.0 - https://znc.in)
2024-04-28 13:13:30 +0200wootehfoot(~wootehfoo@user/wootehfoot) (Client Quit)
2024-04-28 13:12:08 +0200 <ncf> length = void
2024-04-28 13:10:37 +0200wootehfoot(~wootehfoo@user/wootehfoot)
2024-04-28 13:10:01 +0200 <tomsmeding> (random fact: already 6378 saved snippets on the playground)
2024-04-28 13:06:34 +0200 <int-e> (yes, I seem to be circling back to where ski started)
2024-04-28 13:06:15 +0200 <tomsmeding> there is a Natural in base (in Numeric.Natural) but it's just an unsigned 'Integer'
2024-04-28 13:06:06 +0200 <int-e> . o O ( length' = map (const ()) )
2024-04-28 13:05:34 +0200 <ski> it was nice to showcase things like `genericLength xs == (0 :: Natural)', also for infinite `xs'
2024-04-28 13:04:52 +0200 <tomsmeding> there are none in base and I'm salty about that
2024-04-28 13:04:46 +0200 <ski> yes
2024-04-28 13:04:36 +0200 <tomsmeding> inductive peano nats?
2024-04-28 13:04:11 +0200 <ski> (well, i guess it's called `Natural' .. but lambdabot doesn't have that loaded, anymore, afaik)
2024-04-28 13:02:23 +0200qqq(~qqq@92.43.167.61) (Quit: leaving)
2024-04-28 13:02:13 +0200 <ski> int-e : yea, was just thinking about that, in relation to ordering on `Nat'
2024-04-28 13:01:48 +0200 <ski> sounds relevant, tomsmeding
2024-04-28 13:01:48 +0200mrmr1553343(~mrmr@user/mrmr) (Quit: Bye, See ya later!)
2024-04-28 13:01:40 +0200 <int-e> ski: I guess [] <= undefined *could* be defined but the report defines everything in terms of `compare` and [] `compare` undefined has to be bottom
2024-04-28 13:01:19 +0200 <tomsmeding> ski: that would be the Last-Modified http header, right?
2024-04-28 13:01:16 +0200 <yin> *good
2024-04-28 13:01:11 +0200 <yin> goog conversation nontheless
2024-04-28 12:59:41 +0200rosco(~rosco@yp-146-6.tm.net.my)
2024-04-28 12:59:35 +0200 <yin> lol i need to wake up
2024-04-28 12:59:18 +0200 <ski> (it was an answer)
2024-04-28 12:59:06 +0200 <int-e> yin: that wasn't a question
2024-04-28 12:58:53 +0200wootehfoot(~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer)
2024-04-28 12:58:42 +0200paotsaq(~paotsaq@127.209.37.188.rev.vodafone.pt)
2024-04-28 12:58:35 +0200 <yin> int-e: is it clear now?
2024-04-28 12:58:11 +0200 <lambdabot> *Exception: Prelude.undefined
2024-04-28 12:58:09 +0200 <ski> > [0] <= 0:undefined
2024-04-28 12:58:03 +0200 <lambdabot> *Exception: Prelude.undefined
2024-04-28 12:58:02 +0200 <ski> > [0] >= 0:undefined
2024-04-28 12:57:54 +0200paotsaq(~paotsaq@127.209.37.188.rev.vodafone.pt) (Quit: ZNC 1.9.0 - https://znc.in)
2024-04-28 12:56:58 +0200 <lambdabot> False
2024-04-28 12:56:57 +0200 <yin> > [0] >= [0,undefined]
2024-04-28 12:55:45 +0200 <lambdabot> True
2024-04-28 12:55:44 +0200 <tomsmeding> > [1] >= repeat 0
2024-04-28 12:55:31 +0200 <lambdabot> False
2024-04-28 12:55:30 +0200 <yin> > [] >= [0]
2024-04-28 12:55:25 +0200 <lambdabot> False
2024-04-28 12:55:23 +0200 <yin> > [0] >= [0,0]
2024-04-28 12:54:04 +0200 <tomsmeding> hm I guess
2024-04-28 12:53:47 +0200 <lambdabot> False
2024-04-28 12:53:46 +0200 <int-e> > [1,0] >= [1,0,0]
2024-04-28 12:53:12 +0200 <tomsmeding> can somebody tell me why cabal does not consider 1.0 >= 1.0.0
2024-04-28 12:52:26 +0200Lord_of_Life_Lord_of_Life
2024-04-28 12:52:04 +0200wootehfoot(~wootehfoo@user/wootehfoot)
2024-04-28 12:51:16 +0200 <tomsmeding> (had to choose some value)
2024-04-28 12:51:10 +0200 <ski> *nod*