2026/01/15

Newest at the top

2026-01-15 18:43:25 +0100kuribas(~user@2a02-1810-2825-6000-b6e0-77f4-472f-1183.ip6.access.telenet.be) (Remote host closed the connection)
2026-01-15 18:34:09 +0100fp(~Thunderbi@89-27-10-140.bb.dnainternet.fi) fp
2026-01-15 18:24:20 +0100larsivi(~larsivi@user/larsivi) (Quit: WeeChat 4.8.1)
2026-01-15 18:23:37 +0100koz(~koz@121.99.240.58)
2026-01-15 18:22:05 +0100Lycurgus(~juan@user/Lycurgus) (Quit: alsoknownas.renjuan.org ( juan@acm.org ))
2026-01-15 18:14:16 +0100danza(~danza@user/danza) (Remote host closed the connection)
2026-01-15 18:12:52 +0100 <danza> cheers monochrom
2026-01-15 18:12:14 +0100euphores(~SASL_euph@user/euphores) euphores
2026-01-15 18:08:49 +0100 <monochrom> Oh, <=> is iff.
2026-01-15 18:08:38 +0100 <lambdabot> Suggested fix:
2026-01-15 18:08:38 +0100 <lambdabot> Variable not in scope: <=>
2026-01-15 18:08:38 +0100 <lambdabot> error: [GHC-88464]
2026-01-15 18:08:37 +0100 <danza> :t (<=>)
2026-01-15 18:08:36 +0100 <monochrom> (or any syntax)
2026-01-15 18:08:29 +0100 <monochrom> (Hint: They are pros in math content, but not math syntax.)
2026-01-15 18:07:44 +0100 <monochrom> Alternatively, you can legalize "x == y == z" but you say it does not mean "(x == y) == z" or "x == (y == z)". You say it means "x == y && y == z". This is what mathematicians did. (You can trust that they are pros and they know what they're doing, right? Right? >:) )
2026-01-15 18:07:17 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-01-15 18:02:20 +0100 <monochrom> It is surprising but handy that both == and /= (xor) are commutative associative and with identities.
2026-01-15 18:01:16 +0100 <tomsmeding> (because == on Bools is <=>)
2026-01-15 18:00:56 +0100 <monochrom> (Fun fact: But if x,y,z are all Bool, then they are the same. Draw a truth table to see and be shocked. :) )
2026-01-15 18:00:07 +0100 <monochrom> "associativity" talks about whether "(x == y) == z" and "x == (y == z)" are the same or not. So those are the two expressions the hint wants you to look at. If they were the same, can you see a type error?
2026-01-15 17:59:00 +0100doyougnu(~doyougnu@38.175.72.111)
2026-01-15 17:55:35 +0100doyougnu(~doyougnu@38.175.72.111) (Ping timeout: 240 seconds)
2026-01-15 17:52:13 +0100euphores(~SASL_euph@user/euphores) (Quit: Leaving.)
2026-01-15 17:51:01 +0100merijn(~merijn@77.242.116.146) (Ping timeout: 264 seconds)
2026-01-15 17:42:17 +0100ft(~ft@p4fc2a9d7.dip0.t-ipconnect.de) ft
2026-01-15 17:42:06 +0100trickard_(~trickard@cpe-84-98-47-163.wireline.com.au)
2026-01-15 17:41:53 +0100trickard_(~trickard@cpe-84-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2026-01-15 17:34:18 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) (Quit: Leaving...)
2026-01-15 17:30:36 +0100danz65539(~danza@user/danza) (Read error: Connection reset by peer)
2026-01-15 17:29:40 +0100danza(~danza@user/danza) danza
2026-01-15 17:29:33 +0100Lycurgus(~juan@user/Lycurgus) Lycurgus
2026-01-15 17:29:11 +0100rainbyte(~rainbyte@186.22.19.214) rainbyte
2026-01-15 17:25:50 +0100rainbyte(~rainbyte@186.22.19.214) (Read error: Connection reset by peer)
2026-01-15 17:25:08 +0100tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) tzh
2026-01-15 17:23:15 +0100chele(~chele@user/chele) (Remote host closed the connection)
2026-01-15 17:20:51 +0100humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2026-01-15 17:14:11 +0100merijn(~merijn@77.242.116.146) merijn
2026-01-15 17:12:37 +0100merijn(~merijn@77.242.116.146) (Ping timeout: 264 seconds)
2026-01-15 17:07:15 +0100merijn(~merijn@77.242.116.146) merijn
2026-01-15 17:05:13 +0100 <tomsmeding> chromoblob: "authors of language" -- authors of _this_ language. The authors of Python did think this was a good idea
2026-01-15 17:03:56 +0100Inline(~User@cgn-195-14-218-118.nc.de) Inline
2026-01-15 17:03:46 +0100trickard_(~trickard@cpe-84-98-47-163.wireline.com.au)
2026-01-15 17:03:32 +0100trickard_(~trickard@cpe-84-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2026-01-15 17:01:39 +0100bggd(~bgg@user/bggd) (Remote host closed the connection)
2026-01-15 17:00:55 +0100itaipu(~itaipu@168.121.99.54) (Ping timeout: 240 seconds)
2026-01-15 16:56:17 +0100itaipu(~itaipu@168.121.99.54) itaipu
2026-01-15 16:54:05 +0100merijn(~merijn@77.242.116.146) (Ping timeout: 244 seconds)
2026-01-15 16:54:02 +0100itaipu(~itaipu@168.121.99.54) (Ping timeout: 256 seconds)
2026-01-15 16:53:38 +0100catties(~catties@user/meow/catties) catties