Newest at the top
| 2025-06-13 13:40:29 +0200 | rvalue | (~rvalue@user/rvalue) rvalue |
| 2025-06-13 13:37:41 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-13 13:37:21 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-13 13:37:06 +0200 | prdak | (~Thunderbi@user/prdak) (Read error: Connection reset by peer) |
| 2025-06-13 13:34:10 +0200 | qaotsap | (~paotsaq@161.230.89.225) (Ping timeout: 272 seconds) |
| 2025-06-13 13:31:07 +0200 | paotsaq | (~paotsaq@161.230.89.225) |
| 2025-06-13 13:30:44 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-13 13:30:23 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-13 13:22:52 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-13 13:22:32 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-13 13:19:14 +0200 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 260 seconds) |
| 2025-06-13 13:14:50 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-13 13:14:29 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-13 13:10:41 +0200 | prdak | (~Thunderbi@user/prdak) prdak |
| 2025-06-13 13:07:29 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-13 13:07:07 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-13 13:06:52 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-06-13 13:05:40 +0200 | rvalue | (~rvalue@user/rvalue) (Ping timeout: 272 seconds) |
| 2025-06-13 13:01:38 +0200 | jespada | (~jespada@r179-25-11-207.dialup.adsl.anteldata.net.uy) jespada |
| 2025-06-13 13:00:48 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-13 13:00:23 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-13 12:57:57 +0200 | Unicorn_Princess | (~Unicorn_P@user/Unicorn-Princess/x-3540542) Unicorn_Princess |
| 2025-06-13 12:57:25 +0200 | tmciver | (~tim@syn-198-255-177-240.res.spectrum.com) tmciver |
| 2025-06-13 12:57:07 +0200 | tmciver | (~tim@syn-198-255-177-240.res.spectrum.com) (Ping timeout: 268 seconds) |
| 2025-06-13 12:52:58 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-13 12:52:38 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-13 12:51:53 +0200 | <kuribas`> | formatting. |
| 2025-06-13 12:51:39 +0200 | <kuribas`> | Often you need to slightly rethink or rewrite your code to make it typecheck. For example the format library vs printf. |
| 2025-06-13 12:50:32 +0200 | <kuribas`> | I write my code incrementally, and try to keep the types consistent (using typed holes, by following the type errors, rather then trying to coerce the typesystem into checking my code). |
| 2025-06-13 12:48:42 +0200 | vanishingideal | (~vanishing@user/vanishingideal) vanishingideal |
| 2025-06-13 12:48:24 +0200 | <kuribas`> | I suppose "follow the types" is the opposite from "write your implementation first, then typecheck it". |
| 2025-06-13 12:48:02 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |
| 2025-06-13 12:46:10 +0200 | CiaoSen | (~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Ping timeout: 260 seconds) |
| 2025-06-13 12:45:44 +0200 | ljdarj | (~Thunderbi@user/ljdarj) ljdarj |
| 2025-06-13 12:45:22 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-13 12:45:00 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-13 12:44:43 +0200 | <Leary> | kqr: It may depend on the context, but I generally interpret it to mean "derive values (or their implementations) from types". This doesn't necessarily require those values be uniquely specified, as you can often iterate through them simplest-first. |
| 2025-06-13 12:38:30 +0200 | lortabac | (~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) |
| 2025-06-13 12:38:24 +0200 | sajenim | (~sajenim@user/sajenim) (Quit: WeeChat 4.6.3) |
| 2025-06-13 12:36:48 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-06-13 12:36:26 +0200 | <tomsmeding> | true |
| 2025-06-13 12:36:25 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection) |
| 2025-06-13 12:36:05 +0200 | <Leary> | Or very general. |
| 2025-06-13 12:33:39 +0200 | <tomsmeding> | (usually involving GADTs / type families) |
| 2025-06-13 12:33:25 +0200 | <tomsmeding> | but that works only if your types are very precise |
| 2025-06-13 12:33:18 +0200 | <tomsmeding> | there's also the related "hole-driven programming" where you let GHC tell you what type it expects and then you incrementally fill something in that has the right type |
| 2025-06-13 12:32:49 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 248 seconds) |
| 2025-06-13 12:32:41 +0200 | <tomsmeding> | perhaps "types sanity-check your design, if the types don't match with what you're trying to do, don't fight the compiler but re-think your types"? |
| 2025-06-13 12:31:51 +0200 | <tomsmeding> | sounds like a vague advice |
| 2025-06-13 12:30:04 +0200 | <kqr> | What does it mean to "follow the types"? I was going to use it in a particular context, but then I googled it and it seems like people mean very different things with it. |