Newest at the top
| 2025-11-28 22:09:12 +0100 | <EvanR> | so it's not respecting the booleanness or not respecting the laws of a ring |
| 2025-11-28 22:07:39 +0100 | <EvanR> | and negative zero is just zero |
| 2025-11-28 22:06:44 +0100 | <EvanR> | also the concept of negating a bool usually suggests NOT, but negating 1 and perhaps wrapping back to 1 is not that |
| 2025-11-28 22:04:38 +0100 | Googulator | (~Googulato@2a01-036d-0106-4ad8-d9ec-010d-f188-ffcb.pool6.digikabel.hu) |
| 2025-11-28 22:04:10 +0100 | tcard | (~tcard@2400:4051:5801:7500:cf17:befc:ff82:5303) (Quit: Leaving) |
| 2025-11-28 22:04:10 +0100 | jmcantrell | (~weechat@user/jmcantrell) jmcantrell |
| 2025-11-28 22:03:50 +0100 | <EvanR> | it's more clear the code does what the person intended if you use numbers as numbers |
| 2025-11-28 22:02:46 +0100 | <EvanR> | but if you tried to add 1 and 1 to get 2... and perhaps wrapped back to zero, now it's not that |
| 2025-11-28 22:02:29 +0100 | <EvanR> | conventionally the + sign in boolean algebra means OR |
| 2025-11-28 22:01:35 +0100 | trickard_ | trickard |
| 2025-11-28 22:00:40 +0100 | target_i | (~target_i@user/target-i/x-6023099) target_i |
| 2025-11-28 21:54:38 +0100 | <geekosaur> | map fronEnum |
| 2025-11-28 21:53:25 +0100 | <ncf> | no |
| 2025-11-28 21:46:21 +0100 | <gentauro> | Would it make sense that `Bool` had an instance of `Num`? I mean a mapping from `[True, False]` to `[1,0]`? |
| 2025-11-28 21:44:44 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-28 21:33:35 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-11-28 21:28:56 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-28 21:25:57 +0100 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen |
| 2025-11-28 21:25:34 +0100 | annamalai | (~annamalai@157.32.117.148) (Ping timeout: 244 seconds) |
| 2025-11-28 21:23:22 +0100 | acidjnk | (~acidjnk@p200300d6e71719110157f51e13fe5b99.dip0.t-ipconnect.de) acidjnk |
| 2025-11-28 21:17:10 +0100 | myme | (~myme@2a01:799:d5e:5f00:a10a:6bc:6be7:9209) myme |
| 2025-11-28 21:16:11 +0100 | myme1 | (~myme@2a01:799:d5e:5f00:f60f:b1c2:fdec:ad3a) (Ping timeout: 250 seconds) |
| 2025-11-28 21:12:01 +0100 | sergheev | (~sergheev@159.26.108.41) (Client Quit) |
| 2025-11-28 21:11:37 +0100 | sergheev | (~sergheev@159.26.108.41) |
| 2025-11-28 21:07:43 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-11-28 21:02:55 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-28 21:02:25 +0100 | ljdarj | (~Thunderbi@user/ljdarj) (Ping timeout: 264 seconds) |
| 2025-11-28 20:56:41 +0100 | pavonia | (~user@user/siracusa) siracusa |
| 2025-11-28 20:55:51 +0100 | <milan> | Let's go study a little bit more :).. THank you for answers. |
| 2025-11-28 20:55:06 +0100 | tv | (~tv@user/tv) tv |
| 2025-11-28 20:51:37 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds) |
| 2025-11-28 20:45:01 +0100 | sindu | (~sindu@2.148.32.207.tmi.telenormobil.no) (Ping timeout: 264 seconds) |
| 2025-11-28 20:39:06 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection) |
| 2025-11-28 20:38:34 +0100 | <EvanR> | if you call yourself a novice may it sounds better |
| 2025-11-28 20:37:36 +0100 | <milan> | So sad I am noob :/ |
| 2025-11-28 20:37:20 +0100 | <milan> | I really like this language :D |
| 2025-11-28 20:36:45 +0100 | <EvanR> | separate out the specific things lets you put them back together in other ways |
| 2025-11-28 20:36:09 +0100 | <EvanR> | let loop x = x >> loop x in loop (putStrLn "HELLO WORLD") |
| 2025-11-28 20:36:01 +0100 | <milan> | Oh cool :) |
| 2025-11-28 20:35:53 +0100 | <EvanR> | you can also factor out the pattern |
| 2025-11-28 20:35:42 +0100 | <EvanR> | let x = putStrLn "HELLO WORLD" >> x in x -- or chaining infinite prints! |
| 2025-11-28 20:32:05 +0100 | <milan> | Which is possible by chaining multiple print in IO. that guarantees they will be executed multiple times when needed. |
| 2025-11-28 20:31:11 +0100 | <milan> | times. |
| 2025-11-28 20:31:09 +0100 | <milan> | No I was thining why outputing something to external object is encapsulated in IO. My reasoning was that wheter it chages state of this external object correctly or not can't affect our program (until we do some reading) and so IO here is unnecesary. But as pointed out problem with printing multiple times is one when programming would become very unreliable as sometimes we need to output several |
| 2025-11-28 20:29:15 +0100 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) Lord_of_Life |
| 2025-11-28 20:28:55 +0100 | Lord_of_Life | (~Lord@user/lord-of-life/x-2819915) (Ping timeout: 240 seconds) |
| 2025-11-28 20:26:25 +0100 | notzmv | (~umar@user/notzmv) (Ping timeout: 264 seconds) |
| 2025-11-28 20:25:51 +0100 | <EvanR> | print id |
| 2025-11-28 20:25:48 +0100 | <EvanR> | you want it to print the function itself? |
| 2025-11-28 20:25:26 +0100 | <milan> | Okey I think I can see your point. |