2025/09/14

Newest at the top

2025-09-14 21:00:43 +0200caconym747(~caconym@user/caconym) caconym
2025-09-14 21:00:03 +0200caconym747(~caconym@user/caconym) (Quit: bye)
2025-09-14 20:57:48 +0200target_i(~target_i@user/target-i/x-6023099) target_i
2025-09-14 20:56:41 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-14 20:50:11 +0200weary-traveler(~user@user/user363627) user363627
2025-09-14 20:46:14 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-09-14 20:44:11 +0200tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Quit: sdbcjks)
2025-09-14 20:41:01 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-14 20:39:23 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2025-09-14 20:38:05 +0200ChaiTRex(~ChaiTRex@user/chaitrex) ChaiTRex
2025-09-14 20:36:37 +0200ChaiTRex(~ChaiTRex@user/chaitrex) (Ping timeout: 272 seconds)
2025-09-14 20:34:23 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-14 20:33:46 +0200biberu(~biberu@user/biberu) (Read error: Connection reset by peer)
2025-09-14 20:24:42 +0200divlamir(~divlamir@user/divlamir) divlamir
2025-09-14 20:24:29 +0200divlamir(~divlamir@user/divlamir) (Read error: Connection reset by peer)
2025-09-14 20:22:25 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 255 seconds)
2025-09-14 20:10:51 +0200petrichor(~jez@user/petrichor) petrichor
2025-09-14 20:03:49 +0200zzzyin
2025-09-14 19:57:39 +0200AndreiDuma(~AndreiDum@user/AndreiDuma) AndreiDuma
2025-09-14 19:56:41 +0200AndreiDuma(~AndreiDum@user/AndreiDuma) (Quit: My Mac has gone to sleep. ZZZzzz…)
2025-09-14 19:52:55 +0200humasect(~humasect@dyn-192-249-132-90.nexicom.net) humasect
2025-09-14 19:49:35 +0200 <tomsmeding> the tricky thing being that many people don't know about this so they don't do it so you can't really rely on being able to `coerce` safely
2025-09-14 19:48:38 +0200 <tomsmeding> c_wraith: which means that if coerce can break your internal invariants, one should assign stricter roles with explicit role signatures :)
2025-09-14 19:48:19 +0200trickard_trickard
2025-09-14 19:47:39 +0200zzz(~zero@user/zero) zero
2025-09-14 19:47:23 +0200zzz(~zero@user/zero) (Remote host closed the connection)
2025-09-14 19:32:55 +0200trickard_(~trickard@cpe-56-98-47-163.wireline.com.au)
2025-09-14 19:30:30 +0200trickard_(~trickard@cpe-56-98-47-163.wireline.com.au) (Ping timeout: 256 seconds)
2025-09-14 19:18:49 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-14 19:10:12 +0200AndreiDuma(~AndreiDum@user/AndreiDuma) AndreiDuma
2025-09-14 19:07:52 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-09-14 18:57:56 +0200EvanR(~EvanR@user/evanr) (Quit: Leaving)
2025-09-14 18:35:49 +0200sprotte24(~sprotte24@p200300d16f0fa90034a8f8dc2eadcbb1.dip0.t-ipconnect.de)
2025-09-14 18:30:06 +0200petrichor(~jez@user/petrichor) (Ping timeout: 244 seconds)
2025-09-14 18:27:50 +0200lxsameer(~lxsameer@Serene/lxsameer) (Ping timeout: 245 seconds)
2025-09-14 18:21:53 +0200trickard_(~trickard@cpe-56-98-47-163.wireline.com.au)
2025-09-14 18:21:40 +0200trickard_(~trickard@cpe-56-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-09-14 18:13:47 +0200segfaultfizzbuzz(~segfaultf@12.172.219.17) (Ping timeout: 248 seconds)
2025-09-14 18:09:55 +0200 <mreh> neat
2025-09-14 18:09:31 +0200 <monochrom> OK, coerce is also conservative dynamically: in-memory representations are guaranteed to be identical.
2025-09-14 18:08:39 +0200 <monochrom> The type system is also very conservative. :)
2025-09-14 18:08:06 +0200 <c_wraith> ... at least from the type system POV. It may break internal invariants.
2025-09-14 18:06:38 +0200 <c_wraith> the nice thing about Coercible is that it's conservative. If coerce works, it's safe.
2025-09-14 18:06:16 +0200 <mreh> (type checks)
2025-09-14 18:05:40 +0200 <mreh> well, it works
2025-09-14 18:05:23 +0200 <c_wraith> it doesn't have real instances
2025-09-14 18:05:16 +0200 <c_wraith> technically, Coercible is magic
2025-09-14 18:03:47 +0200 <geekosaur> just the rules for implicit `Coercible` constraints. Phantom types are automatically compatible
2025-09-14 18:02:57 +0200 <mreh> is that some GHC magic?
2025-09-14 18:00:46 +0200 <mreh> really...