Newest at the top
| 2025-05-03 22:08:20 +0200 | <r-sta> | what the dependent outcome would be |
| 2025-05-03 22:08:13 +0200 | <r-sta> | because i couldnt infer from the types |
| 2025-05-03 22:08:10 +0200 | <hellwolf> | what does visibility mean here? since you can also use type variables without vdq? |
| 2025-05-03 22:07:59 +0200 | <r-sta> | ie i could return Vertex, but not Vertex Down |
| 2025-05-03 22:07:39 +0200 | <r-sta> | i had to erase them. like, it would return up or down from flat, but these couldnt have different type annotations |
| 2025-05-03 22:07:13 +0200 | <int-e> | yes |
| 2025-05-03 22:07:12 +0200 | <r-sta> | i had like a flippy thing for trading, it had 3 states up down flat, but i couldnt make a class with the singletons appearing at the output |
| 2025-05-03 22:06:44 +0200 | <r-sta> | type erasure is what means we dont need types at runtime right? |
| 2025-05-03 22:05:42 +0200 | Square | (~Square@user/square) (Remote host closed the connection) |
| 2025-05-03 22:05:39 +0200 | <r-sta> | int-e: ok cool thanks |
| 2025-05-03 22:05:34 +0200 | <r-sta> | like you have to specify the type... |
| 2025-05-03 22:05:08 +0200 | <int-e> | https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0378-dependent-type-design.rs… says "The forall vs foreach part governs erasure: foralls are erased, while foreachs are retained." |
| 2025-05-03 22:04:08 +0200 | <r-sta> | "visible dependent quantification" |
| 2025-05-03 22:02:24 +0200 | Square | (~Square@user/square) Square |
| 2025-05-03 22:01:36 +0200 | <r-sta> | (i also dont understand what the arrow is doing there) |
| 2025-05-03 22:01:23 +0200 | <r-sta> | eg. foreach a -> ty |
| 2025-05-03 22:01:18 +0200 | Square | (~Square@user/square) (Remote host closed the connection) |
| 2025-05-03 22:01:08 +0200 | <r-sta> | i have never seen this before |
| 2025-05-03 22:01:02 +0200 | <r-sta> | it mentions foreach |
| 2025-05-03 22:00:58 +0200 | <r-sta> | im trying to read this https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0281-visible-forall.rst |
| 2025-05-03 22:00:58 +0200 | r-sta | (~r-sta@206-122-61-5.reverse.tnp.net.uk) |
| 2025-05-03 21:57:03 +0200 | la1n2 | (~la1n@176.59.162.120) (Read error: Connection reset by peer) |
| 2025-05-03 21:54:14 +0200 | la1n2 | (~la1n@176.59.162.120) |
| 2025-05-03 21:53:56 +0200 | JuanDaugherty | (~juan@user/JuanDaugherty) JuanDaugherty |
| 2025-05-03 21:39:21 +0200 | euleritian | (~euleritia@ip4d17f82f.dynamic.kabel-deutschland.de) |
| 2025-05-03 21:39:01 +0200 | euleritian | (~euleritia@dynamic-176-000-010-081.176.0.pool.telefonica.de) (Read error: Connection reset by peer) |
| 2025-05-03 21:36:24 +0200 | euleritian | (~euleritia@dynamic-176-000-010-081.176.0.pool.telefonica.de) |
| 2025-05-03 21:35:27 +0200 | euleritian | (~euleritia@dynamic-176-006-129-007.176.6.pool.telefonica.de) (Ping timeout: 268 seconds) |
| 2025-05-03 21:32:06 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) |
| 2025-05-03 21:30:27 +0200 | __jmcantrell__ | (~weechat@user/jmcantrell) jmcantrell |
| 2025-05-03 21:28:35 +0200 | __jmcantrell__ | (~weechat@user/jmcantrell) (Ping timeout: 272 seconds) |
| 2025-05-03 21:28:33 +0200 | sabathan2 | (~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Read error: Connection reset by peer) |
| 2025-05-03 21:25:02 +0200 | tromp | (~textual@2001:1c00:3487:1b00:31c9:5f27:18bf:4d4e) |
| 2025-05-03 21:22:54 +0200 | tromp | (~textual@2001:1c00:3487:1b00:31c9:5f27:18bf:4d4e) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2025-05-03 21:21:36 +0200 | j1n37 | (~j1n37@user/j1n37) (Ping timeout: 276 seconds) |
| 2025-05-03 21:21:01 +0200 | j1n37- | (~j1n37@user/j1n37) j1n37 |
| 2025-05-03 21:21:00 +0200 | weary-traveler | (~user@user/user363627) user363627 |
| 2025-05-03 21:20:33 +0200 | <[exa]> | Liamzee: and yeah with the prototype it doesn't really matter if it's super broken or not. :D |
| 2025-05-03 21:20:05 +0200 | __jmcantrell__ | (~weechat@user/jmcantrell) jmcantrell |
| 2025-05-03 21:19:13 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 244 seconds) |
| 2025-05-03 21:18:39 +0200 | <[exa]> | but yeah more like I'm doing it wrong |
| 2025-05-03 21:18:22 +0200 | <[exa]> | monochrom: at the minimum it gives ways to describe both stuff with all references "resolved" and stuff where things are behind references. And likely many states in between. |
| 2025-05-03 21:18:04 +0200 | __jmcantrell__ | (~weechat@user/jmcantrell) (Ping timeout: 252 seconds) |
| 2025-05-03 21:00:42 +0200 | caconym7 | (~caconym@user/caconym) caconym |
| 2025-05-03 21:00:03 +0200 | caconym7 | (~caconym@user/caconym) (Quit: bye) |
| 2025-05-03 20:55:57 +0200 | <haskellbridge> | <Liamzee> thanks |
| 2025-05-03 20:55:34 +0200 | target_i | (~target_i@user/target-i/x-6023099) target_i |
| 2025-05-03 20:54:37 +0200 | <monochrom> | Or maybe I still don't heh. |
| 2025-05-03 20:54:36 +0200 | wootehfoot | (~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer) |
| 2025-05-03 20:54:28 +0200 | <monochrom> | Or should it be "{name :: String, age :: Int, id :: f ()}"? Then I can see what to do with f. |