Newest at the top
| 2026-01-01 03:43:37 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-01-01 03:10:37 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 252 seconds) |
| 2026-01-01 03:06:39 +0100 | bitdex_ | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2026-01-01 03:04:13 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2026-01-01 03:02:11 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 252 seconds) |
| 2026-01-01 03:01:36 +0100 | jmcantrell | (~weechat@user/jmcantrell) jmcantrell |
| 2026-01-01 03:00:55 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) ChaiTRex |
| 2026-01-01 03:00:26 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) (Remote host closed the connection) |
| 2026-01-01 03:00:01 +0100 | peterbecich | (~Thunderbi@71.84.33.135) (Ping timeout: 246 seconds) |
| 2026-01-01 02:53:30 +0100 | aman | (~aman@user/aman) aman |
| 2026-01-01 02:50:44 +0100 | Tuplanolla | (~Tuplanoll@88-114-88-95.elisa-laajakaista.fi) (Quit: Leaving.) |
| 2026-01-01 02:44:35 +0100 | rainbyte_ | (~rainbyte@186.22.19.214) (Ping timeout: 240 seconds) |
| 2026-01-01 02:43:41 +0100 | rainbyte | (~rainbyte@186.22.19.214) rainbyte |
| 2026-01-01 02:38:09 +0100 | rainbyte | (~rainbyte@186.22.19.214) (Ping timeout: 244 seconds) |
| 2026-01-01 02:37:59 +0100 | rainbyte_ | (~rainbyte@186.22.19.214) rainbyte |
| 2026-01-01 02:30:56 +0100 | vanishingideal | (~vanishing@user/vanishingideal) (Ping timeout: 240 seconds) |
| 2026-01-01 02:24:56 +0100 | divlamir | (~divlamir@user/divlamir) divlamir |
| 2026-01-01 02:24:43 +0100 | divlamir | (~divlamir@user/divlamir) (Read error: Connection reset by peer) |
| 2026-01-01 02:19:25 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2026-01-01 02:15:11 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-01-01 02:13:07 +0100 | omidmash8 | omidmash |
| 2026-01-01 02:13:07 +0100 | omidmash | (~omidmash@user/omidmash) (Ping timeout: 265 seconds) |
| 2026-01-01 02:10:34 +0100 | omidmash8 | (~omidmash@user/omidmash) omidmash |
| 2026-01-01 02:02:55 +0100 | Square3 | (~Square@user/square) (Ping timeout: 240 seconds) |
| 2026-01-01 02:00:52 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2026-01-01 01:57:37 +0100 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Ping timeout: 250 seconds) |
| 2026-01-01 01:54:20 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-01-01 01:48:51 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) ChaiTRex |
| 2026-01-01 01:48:20 +0100 | ChaiTRex | (~ChaiTRex@user/chaitrex) (Remote host closed the connection) |
| 2026-01-01 01:41:35 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2026-01-01 01:37:26 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-01-01 01:32:33 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2026-01-01 01:30:16 +0100 | Tuplanolla1 | Tuplanolla |
| 2026-01-01 01:23:35 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2026-01-01 01:19:14 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-01-01 01:15:02 +0100 | <janus> | such a program, without interleaving, would have ambiguous types and compilation would fail. since it wouldn't be able to take the 'output' and propagate it to other constraints |
| 2026-01-01 01:13:38 +0100 | <janus> | then, it should evaluate the fundep and that should give it enough info to find the 'principal' type |
| 2026-01-01 01:13:17 +0100 | <janus> | maybe the easiest example should be something that uses mtl, and somehow has polymorphic types in both the 'input' and the 'output' type of a fundep. now, the surrounding program somehow determines one of these, and the typechecker should be able to run enough of 'regular' constraints to find out that there is this constraint on input and output |
| 2026-01-01 01:10:36 +0100 | <janus> | i still can't imagine a program that would require something like that |
| 2026-01-01 01:10:07 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds) |
| 2026-01-01 01:10:04 +0100 | <janus> | right. so it's not strictly MPTC that require interleaving |
| 2026-01-01 01:09:38 +0100 | <geekosaur> | inference isn't possible otherwise |
| 2026-01-01 01:09:24 +0100 | <geekosaur> | my understanding is that MPTCs are really only usable with either fundeps or TFs |
| 2026-01-01 01:07:51 +0100 | <janus> | if i understand correctly, fundeps only make sense with MPTC, and since fundeps are so prevalent with mtl, i wonder whether that is why you said MPTC instead of saying fundeps. since for all practical typecheckers, they will need to support both |
| 2026-01-01 01:06:47 +0100 | <janus> | [exa]: is it really just MPTC that would require type-level computation interleaved with previous typechecking? or is it about fundeps? |
| 2026-01-01 01:05:18 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-01-01 01:03:55 +0100 | traxex | (traxex@user/traxex) (Ping timeout: 264 seconds) |
| 2026-01-01 00:57:15 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2026-01-01 00:55:55 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) () |
| 2026-01-01 00:52:38 +0100 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |