Newest at the top
| 2025-03-03 12:18:14 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 260 seconds) |
| 2025-03-03 12:12:10 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-03-03 12:07:26 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) ash3en |
| 2025-03-03 12:01:09 +0100 | Digit | (~user@user/digit) (Ping timeout: 248 seconds) |
| 2025-03-03 12:00:02 +0100 | Digitteknohippie | (~user@user/digit) Digit |
| 2025-03-03 11:58:29 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 248 seconds) |
| 2025-03-03 11:49:51 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-03-03 11:41:47 +0100 | <tomsmeding> | how much value you ascribe to this argument depends on how acceptable you think it is to need HLS to work productively. :) |
| 2025-03-03 11:41:25 +0100 | <tomsmeding> | a possible argument in this debate: the more you use polymorphic typeclass methods instead of monomorphic ones (where the latter would have been possible), the less readable your code gets without HLS telling what type things have |
| 2025-03-03 11:39:03 +0100 | <tomsmeding> | to which there's no general consensus other than that 'map' hasn't been removed yet, so do what you think is right |
| 2025-03-03 11:38:35 +0100 | <carbolymer> | yeah ) |
| 2025-03-03 11:38:28 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 268 seconds) |
| 2025-03-03 11:38:18 +0100 | <tomsmeding> | carbolymer: I guess it comes down to which side of the debate you're on regarding "should we have 'map' in addition to 'fmap'" :) |
| 2025-03-03 11:37:28 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 245 seconds) |
| 2025-03-03 11:34:39 +0100 | lortabac | (~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) lortabac |
| 2025-03-03 11:33:37 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-03 11:33:17 +0100 | tabaqui1 | (~root@87.200.129.102) tabaqui |
| 2025-03-03 11:31:21 +0100 | lortabac | (~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) (Ping timeout: 246 seconds) |
| 2025-03-03 11:30:25 +0100 | xff0x | (~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 252 seconds) |
| 2025-03-03 11:27:05 +0100 | <carbolymer> | the downside is that compiler errors are not very readable with `IsList` |
| 2025-03-03 11:25:43 +0100 | <carbolymer> | I prefer IsList over Map.fromList for example, because I can easily change the collection type and don't worry about updating imports everywhere. Why do you consider its only use case `OverloadedLists`? |
| 2025-03-03 11:23:59 +0100 | <merijn> | carbolymer: I mean, the main (only) use case for IsList is `OverloadedLists` in which case the instance should generally be inferred and inlining known instances is a pretty trivial optimisation I'd assume GHC gets right |
| 2025-03-03 11:23:43 +0100 | lxsameer | (~lxsameer@Serene/lxsameer) (Ping timeout: 245 seconds) |
| 2025-03-03 11:22:03 +0100 | <carbolymer> | yes, def, but is it worth providing monomorphic versions of those? |
| 2025-03-03 11:21:24 +0100 | <tomsmeding> | if you don't, you should probably re-export toList and fromList from IsList |
| 2025-03-03 11:20:25 +0100 | <carbolymer> | If you were writing a module exposing an API for a collection, together with IsList instance, would you expose monomorphic toList & fromList functions as well? |
| 2025-03-03 11:18:27 +0100 | s3 | (~s3@user/bn) bn |
| 2025-03-03 11:18:27 +0100 | s3 | (~s3@212.225.225.72) (Changing host) |
| 2025-03-03 11:12:12 +0100 | tromp | (~textual@2a02:a210:cba:8500:4189:9487:9abd:f78) |
| 2025-03-03 11:10:34 +0100 | tromp | (~textual@2a02:a210:cba:8500:4189:9487:9abd:f78) (Quit: My iMac has gone to sleep. ZZZzzz…) |
| 2025-03-03 11:10:10 +0100 | econo_ | (uid147250@id-147250.tinside.irccloud.com) (Quit: Connection closed for inactivity) |
| 2025-03-03 11:04:52 +0100 | poscat0x04 | (~poscat@user/poscat) poscat |
| 2025-03-03 11:04:42 +0100 | lxsameer | (~lxsameer@Serene/lxsameer) lxsameer |
| 2025-03-03 11:04:38 +0100 | poscat | (~poscat@user/poscat) (Ping timeout: 252 seconds) |
| 2025-03-03 11:04:29 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-03-03 11:02:00 +0100 | ephilalethes | (~noumenon@2001:d08:1a03:d771:aa7e:eaff:fede:ff94) noumenon |
| 2025-03-03 11:01:46 +0100 | noumenon | (~noumenon@2001:d08:1a03:d771:aa7e:eaff:fede:ff94) (Client Quit) |
| 2025-03-03 11:01:38 +0100 | ephilalethes | (~noumenon@2001:d08:1a03:d771:aa7e:eaff:fede:ff94) (Read error: Connection reset by peer) |
| 2025-03-03 11:01:11 +0100 | noumenon | (~noumenon@2001:d08:1a03:d771:aa7e:eaff:fede:ff94) noumenon |
| 2025-03-03 10:58:38 +0100 | tromp | (~textual@2a02:a210:cba:8500:4189:9487:9abd:f78) |
| 2025-03-03 10:58:33 +0100 | __monty__ | (~toonn@user/toonn) toonn |
| 2025-03-03 10:53:48 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 276 seconds) |
| 2025-03-03 10:51:12 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 276 seconds) |
| 2025-03-03 10:49:01 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-03-03 10:46:33 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-03 10:37:06 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 246 seconds) |
| 2025-03-03 10:31:31 +0100 | ash3en | (~Thunderbi@2a03:7846:b6eb:101:93ac:a90a:da67:f207) (Quit: ash3en) |
| 2025-03-03 10:19:07 +0100 | AlexZenon | (~alzenon@178.34.160.108) |
| 2025-03-03 10:15:14 +0100 | lortabac | (~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) |
| 2025-03-03 10:14:42 +0100 | AlexZenon | (~alzenon@178.34.162.44) (Ping timeout: 272 seconds) |