Newest at the top
| 2025-01-17 07:22:37 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds) |
| 2025-01-17 07:20:51 +0100 | <Leary> | (the other option is to just use `<|>` on `Maybe`) |
| 2025-01-17 07:19:24 +0100 | <Leary> | jle`: `Data.Monoid.First` exists for a reason; `Maybe . Data.Semigroup.First` can't just stop at the first `Just`. |
| 2025-01-17 07:18:03 +0100 | <haskellbridge> | <Bowuigi> homo just provide a wrapper that exports the safe parts of Hugs.Prelude and overimport just in case, that's the best option I can think of rn |
| 2025-01-17 07:17:42 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-17 07:14:58 +0100 | _xor | (~xor@ip-66-42-132-175.dynamic.fuse.net) _xor |
| 2025-01-17 07:12:43 +0100 | _xor | (~xor@ip-66-42-132-175.dynamic.fuse.net) (Quit: Ping timeout (120 seconds)) |
| 2025-01-17 07:10:34 +0100 | <jle`> | i'm even doing x <> (y <> ...) the good way |
| 2025-01-17 07:10:08 +0100 | <jle`> | i guess it just compiles better? i would have expected them to end up being the same |
| 2025-01-17 07:09:52 +0100 | <jle`> | and using Endo . const . Just |
| 2025-01-17 07:09:42 +0100 | <jle`> | (and applying the second to Nothing) |
| 2025-01-17 07:09:28 +0100 | <jle`> | huh kind of funny but (<>) for Maybe (First a) seems to be slower than (<>) for Endo (Maybe a) |
| 2025-01-17 07:07:15 +0100 | alp | (~alp@2001:861:8ca0:4940:8a73:f3f6:adcb:ed3) |
| 2025-01-17 07:07:09 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 260 seconds) |
| 2025-01-17 07:05:56 +0100 | euleritian | (~euleritia@77.23.250.232) |
| 2025-01-17 07:05:13 +0100 | euleritian | (~euleritia@ip4d17fae8.dynamic.kabel-deutschland.de) (Read error: Connection reset by peer) |
| 2025-01-17 07:03:07 +0100 | Sgeo | (~Sgeo@user/sgeo) Sgeo |
| 2025-01-17 07:02:39 +0100 | takuan | (~takuan@178-116-218-225.access.telenet.be) |
| 2025-01-17 06:59:48 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-17 06:57:08 +0100 | Sgeo | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
| 2025-01-17 06:53:11 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2025-01-17 06:48:51 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-17 06:46:14 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 252 seconds) |
| 2025-01-17 06:43:28 +0100 | Sgeo | (~Sgeo@user/sgeo) Sgeo |
| 2025-01-17 06:37:54 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds) |
| 2025-01-17 06:35:47 +0100 | weary-traveler | (~user@user/user363627) (Remote host closed the connection) |
| 2025-01-17 06:34:48 +0100 | <homo> | I don't think it's a good idea to port microhs base without adjusting hugsbase first, and it might be necessary to also adjust hugs interpreter itself before adjusting hugsbase |
| 2025-01-17 06:30:47 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-17 06:30:35 +0100 | <homo> | reading the source code of hugs a lot of modules from base package already use primitives from hugsbase package, but that is not enough to shut name clashes |
| 2025-01-17 06:26:27 +0100 | <homo> | Bowuigi anyway, those name clashes are very persistent, you either have to use qualified imports or to explicitly shut up Hugs.Prelude, but you don't want to explicitly shut up Hugs.Prelude because code read by ghc and microhs will not compile |
| 2025-01-17 06:21:13 +0100 | Sgeo | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
| 2025-01-17 06:20:09 +0100 | <homo> | also keep in mind libraries that hugs uses are the same libraries that ghc used 20 years ago, so if someone decides to fork hugs, there is a lot of tedious work to keep libraries up-to-date |
| 2025-01-17 06:20:00 +0100 | michalz | (~michalz@185.246.207.215) |
| 2025-01-17 06:19:49 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds) |
| 2025-01-17 06:16:35 +0100 | <homo> | it already reuses some of microhs base library to avoid code duplication, I'd say it's just tedious to patch every individual module, and some modules are extremely tedious because of language extensions |
| 2025-01-17 06:15:26 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2025-01-17 06:14:56 +0100 | <haskellbridge> | <Bowuigi> That's so odd, why did they do that. How feasible is porting the microhs base library to Hugs? Using Hugs primitives, ofc |
| 2025-01-17 06:14:09 +0100 | <homo> | s/it/Hugs.Prelude/ |
| 2025-01-17 06:13:52 +0100 | <homo> | it also clashes with Data.Foldable and Data.Functor |
| 2025-01-17 06:13:23 +0100 | <homo> | Hugs.Prelude also clashes with Control.Exception |
| 2025-01-17 06:12:39 +0100 | <haskellbridge> | <Bowuigi> Diff is your friend here, any changes will stand out |
| 2025-01-17 06:12:27 +0100 | <homo> | Bowuigi for example, System.IO.Error clashes with Control.Exception |
| 2025-01-17 06:09:44 +0100 | <homo> | thanks for idea, but I don't remember if I did something else besides removing forall from instance |
| 2025-01-17 06:08:50 +0100 | <haskellbridge> | <Bowuigi> Also which name clashes? The lack of applicative and functor operators is annoying but that can be solved easily |
| 2025-01-17 06:08:06 +0100 | dnerdhm^ | (~dnerdhm@108.192.66.114) |
| 2025-01-17 06:08:05 +0100 | dsrt^ | (~dsrt@108.192.66.114) |
| 2025-01-17 06:07:49 +0100 | <haskellbridge> | <Bowuigi> Also play with Hugs' options, some may help with the recursion issues you're having |
| 2025-01-17 06:05:52 +0100 | <haskellbridge> | <Bowuigi> I have no experience with yacc sadly, but some sed/awk could fix your instance forall issues. Just keep the original code around and at build time run a script that replaces "instance forall [^\.]." by just "instance", you don't have to remove them by hand |
| 2025-01-17 06:05:02 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 272 seconds) |
| 2025-01-17 06:04:34 +0100 | nschoe | (~nschoe@82-65-202-30.subs.proxad.net) nschoe |