Newest at the top
| 2024-07-19 02:54:13 +0200 | ystael | (~ystael@user/ystael) (Ping timeout: 248 seconds) |
| 2024-07-19 02:45:45 +0200 | ystael | (~ystael@user/ystael) |
| 2024-07-19 02:41:36 +0200 | <Unicorn_Princess> | thanks, thought it would be something like that |
| 2024-07-19 02:38:57 +0200 | <c_wraith> | (More specifically - when ScopedTypeVariables is enabled, type variables appearing in a class definition's head are available to all declarations inside the class) |
| 2024-07-19 02:37:43 +0200 | <c_wraith> | Unicorn_Princess: enable ScopedTypeVariables. In that specific case, that's all you need to do. (unlike top-level type declarations, it doesn't need a forall to bring the variable into scope) |
| 2024-07-19 02:36:18 +0200 | machinedgod | (~machinedg@d173-183-246-216.abhsia.telus.net) (Ping timeout: 276 seconds) |
| 2024-07-19 02:35:53 +0200 | <Unicorn_Princess> | how can i specify that a type in a nested signature is the same as the type in the class declaration? example: https://paste.tomsmeding.com/xbrjE1uC |
| 2024-07-19 02:33:11 +0200 | xff0x | (~xff0x@2405:6580:b080:900:71aa:4bc6:5c8f:1add) |
| 2024-07-19 02:33:10 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) |
| 2024-07-19 02:21:36 +0200 | Unicorn_Princess | (~Unicorn_P@user/Unicorn-Princess/x-3540542) |
| 2024-07-19 02:15:56 +0200 | ChaiTRex | (~ChaiTRex@user/chaitrex) |
| 2024-07-19 02:10:57 +0200 | mrmr155334346 | (~mrmr@user/mrmr) (Ping timeout: 276 seconds) |
| 2024-07-19 02:01:51 +0200 | xff0x | (~xff0x@2405:6580:b080:900:71aa:4bc6:5c8f:1add) (Ping timeout: 246 seconds) |
| 2024-07-19 01:59:29 +0200 | yin | (~yin@user/zero) (Quit: leaving) |
| 2024-07-19 01:55:14 +0200 | zero | (~z@user/zero) |
| 2024-07-19 01:54:31 +0200 | Tuplanolla | (~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.) |
| 2024-07-19 01:53:18 +0200 | zero | (~z@user/zero) (Quit: quit) |
| 2024-07-19 01:43:58 +0200 | gmg | (~user@user/gehmehgeh) (Quit: Leaving) |
| 2024-07-19 01:43:35 +0200 | ddellacosta | (~ddellacos@ool-44c73d29.dyn.optonline.net) |
| 2024-07-19 01:42:37 +0200 | pavonia | (~user@user/siracusa) |
| 2024-07-19 01:41:37 +0200 | ddellacosta | (~ddellacos@ool-44c73d29.dyn.optonline.net) (Ping timeout: 252 seconds) |
| 2024-07-19 01:34:47 +0200 | tomku | (~tomku@user/tomku) |
| 2024-07-19 01:34:33 +0200 | tomku | (~tomku@user/tomku) (Ping timeout: 276 seconds) |
| 2024-07-19 01:19:36 +0200 | mreh | (~matthew@host86-160-168-12.range86-160.btcentralplus.com) (Ping timeout: 276 seconds) |
| 2024-07-19 01:16:43 +0200 | monochrom | (trebla@216.138.220.146) (Quit: ZNC 1.9.0+deb2build3 - https://znc.in) |
| 2024-07-19 01:15:01 +0200 | noumenon | (~noumenon@113.51-175-156.customer.lyse.net) (Quit: Leaving) |
| 2024-07-19 01:09:02 +0200 | Guest18 | (~Guest18@2605:59c8:26f7:4e10:241b:ad0:4a05:c733) (Quit: Client closed) |
| 2024-07-19 00:59:14 +0200 | zero | (~z@user/zero) |
| 2024-07-19 00:58:17 +0200 | zero | (~z@user/zero) (Remote host closed the connection) |
| 2024-07-19 00:53:36 +0200 | misterfish | (~misterfis@84.53.85.146) (Ping timeout: 276 seconds) |
| 2024-07-19 00:47:43 +0200 | Midjak | (~MarciZ@82.66.147.146) (Quit: This computer has gone to sleep) |
| 2024-07-19 00:42:55 +0200 | noumenon | (~noumenon@113.51-175-156.customer.lyse.net) |
| 2024-07-19 00:28:10 +0200 | misterfish | (~misterfis@84.53.85.146) |
| 2024-07-19 00:27:11 +0200 | misterfish | (~misterfis@84.53.85.146) (Ping timeout: 252 seconds) |
| 2024-07-19 00:26:16 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2024-07-19 00:24:34 +0200 | yin | (~yin@user/zero) |
| 2024-07-19 00:23:37 +0200 | euleritian | (~euleritia@dynamic-176-004-239-040.176.4.pool.telefonica.de) |
| 2024-07-19 00:23:24 +0200 | euleritian | (~euleritia@dynamic-176-005-130-223.176.5.pool.telefonica.de) (Ping timeout: 260 seconds) |
| 2024-07-19 00:22:54 +0200 | <c_wraith> | They're just a bit of unnecessary syntactic sugar... except in pattern synonyms, where they're the only way to use functions while destructuring values. |
| 2024-07-19 00:22:05 +0200 | misterfish | (~misterfis@84.53.85.146) |
| 2024-07-19 00:21:45 +0200 | <c_wraith> | yeah. Honestly, I don't see a lot of value in using them outside of pattern synonyms |
| 2024-07-19 00:21:25 +0200 | <mreh> | similar to how you can pattenr match in pattern guards |
| 2024-07-19 00:20:37 +0200 | <mreh> | aha |
| 2024-07-19 00:20:13 +0200 | <c_wraith> | it calls the function on the left side of the -> on the value being matched, and then matches the result of that function against the pattern on the right. |
| 2024-07-19 00:19:29 +0200 | <c_wraith> | that's a view pattern |
| 2024-07-19 00:19:07 +0200 | CiaoSen | (~Jura@2a05:5800:2b2:a300:e6b9:7aff:fe80:3d03) (Ping timeout: 252 seconds) |
| 2024-07-19 00:18:53 +0200 | <mreh> | what is this syntax in a pattern match? `boundingBox (G.Bitmap (G.bitmapSize -> (w, h)))` |
| 2024-07-19 00:16:55 +0200 | falafel | (~falafel@2a0c:5a84:e301:4d01::5c13) (Ping timeout: 252 seconds) |
| 2024-07-19 00:15:20 +0200 | pointlessslippe1 | (~pointless@212.82.82.3) |
| 2024-07-19 00:09:47 +0200 | ChaiTRex | (~ChaiTRex@user/chaitrex) (Quit: ChaiTRex) |