2024/12/28

Newest at the top

2024-12-28 17:31:27 +0100 <enikar> maybe don't do all the stuff in main will help
2024-12-28 17:31:14 +0100 <int-e> (and there are more keywords to find)
2024-12-28 17:30:26 +0100 <int-e> plitter: but the error you're getting is because `if` is a keyword
2024-12-28 17:28:57 +0100 <int-e> plitter: you'd want a single `let` block
2024-12-28 17:27:41 +0100 <plitter> was interested in at the end. Is there some compiler options that will let me do that? Or amI on the wrong track?
2024-12-28 17:27:39 +0100 <plitter> I'm doing an advent of code https://adventofcode.com/2015/day/7 and thought I could use haskell to just input all the instructions but translated to haskell https://termbin.com/9u1q. But getting an error because of what I'm assuming is out of scope variable https://termbin.com/o4kn. I thought that haskell would wait with trying to input values until the end. And that I could just print the value I
2024-12-28 17:27:16 +0100lxsameer(~lxsameer@Serene/lxsameer) lxsameer
2024-12-28 17:21:13 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 252 seconds)
2024-12-28 17:20:00 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Ping timeout: 264 seconds)
2024-12-28 17:16:56 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-28 17:16:11 +0100 <hellwolf> what is it?
2024-12-28 17:16:07 +0100 <hellwolf> not sure how using "labels" would look like.
2024-12-28 17:15:57 +0100 <hellwolf> asking for partially "anonymous" fields seems a stretch. Considering that in most languages, you don't have such a thing.
2024-12-28 17:15:09 +0100 <hellwolf> but I probably should just export all fields.
2024-12-28 17:14:24 +0100simplystuart(~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Remote host closed the connection)
2024-12-28 17:14:19 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 265 seconds)
2024-12-28 17:14:11 +0100 <hellwolf> labels, lenses, OverloadedRecordDot seems its own paradigm.
2024-12-28 17:14:01 +0100simplystuart(~simplystu@c-75-75-152-164.hsd1.pa.comcast.net)
2024-12-28 17:13:07 +0100 <haskellbridge> <loonycyborg> I'm wondering why record syntax is made in such a way you can't use indentation with it to get rid of {}
2024-12-28 17:12:44 +0100 <haskellbridge> <loonycyborg> were there any proposals to change that?
2024-12-28 17:12:35 +0100 <haskellbridge> <loonycyborg> I'm wondering why record syntax is made in such a way you can't use indentation with it
2024-12-28 17:12:03 +0100 <hellwolf> :)
2024-12-28 17:12:01 +0100 <hellwolf> 12-28 18:08 <int-e> hellwolf: hack hack hack: https://paste.tomsmeding.com/P0Xif3Ga
2024-12-28 17:09:47 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-28 17:08:52 +0100 <int-e> hellwolf: hack hack hack: https://paste.tomsmeding.com/P0Xif3Ga
2024-12-28 17:07:28 +0100euleritian(~euleritia@dynamic-176-006-135-074.176.6.pool.telefonica.de)
2024-12-28 17:06:15 +0100 <geekosaur> like I said, wart
2024-12-28 17:06:07 +0100 <geekosaur> nor a way IIRC to say "this is actually used"; ghc's way to say "not used" is prefix underscore, but that messes with other ways to use the selector
2024-12-28 17:05:33 +0100 <geekosaur> sadly there's no way to disable it only for some things
2024-12-28 17:04:52 +0100 <geekosaur> I don't like OverloadedRecordDot much but it is at least a partial solution to records
2024-12-28 17:04:46 +0100 <__monty__> Seems like a case of an overeager warning. There's probably a way to disable a warning with a pragma?
2024-12-28 17:04:39 +0100euleritian(~euleritia@dynamic-176-006-135-074.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2024-12-28 17:04:27 +0100euleritian(~euleritia@dynamic-176-006-135-074.176.6.pool.telefonica.de)
2024-12-28 17:04:25 +0100aerphanas(~aerphanas@user/aerphanas) (Quit: WeeChat 3.8)
2024-12-28 17:04:24 +0100 <geekosaur> it is best to treat traditional record syntax as a wart, and either work around it or switch to a newer one (labels, OverloadedRecordDot, lenses)
2024-12-28 17:04:08 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2024-12-28 16:58:21 +0100 <hellwolf> then there is a warning of that the function is not used.
2024-12-28 16:57:08 +0100 <__monty__> But it doesn't actually make the field inaccessible so I'm not sure it's a good idea.
2024-12-28 16:56:42 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 246 seconds)
2024-12-28 16:56:32 +0100 <__monty__> You can selectively export field accessors from a module IIRC.
2024-12-28 16:55:21 +0100euleritian(~euleritia@dynamic-176-006-135-074.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2024-12-28 16:54:18 +0100euleritian(~euleritia@dynamic-176-006-135-074.176.6.pool.telefonica.de)
2024-12-28 16:53:03 +0100 <hellwolf> hmm, so, record syntax wise, you can not define a field that does not have a function, while others have?
2024-12-28 16:52:14 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-28 16:46:12 +0100__monty__(~toonn@user/toonn) toonn
2024-12-28 16:45:48 +0100euleritian(~euleritia@dynamic-176-006-135-074.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2024-12-28 16:39:55 +0100alp(~alp@128-79-174-146.hfc.dyn.abo.bbox.fr)
2024-12-28 16:38:57 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 248 seconds)
2024-12-28 16:34:21 +0100merijn(~merijn@128-137-045-062.dynamic.caiway.nl) merijn
2024-12-28 16:32:28 +0100euleritian(~euleritia@dynamic-176-006-135-074.176.6.pool.telefonica.de)