2024/05/01

Newest at the top

2024-05-01 20:05:51 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2024-05-01 20:05:34 +0200gaff(~gaff@49.207.212.165) ()
2024-05-01 20:04:02 +0200hseg(~gesh@77.137.75.224)
2024-05-01 19:59:48 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-01 19:58:04 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2024-05-01 19:57:37 +0200justsomeguy(~justsomeg@user/justsomeguy) (Ping timeout: 272 seconds)
2024-05-01 19:54:54 +0200 <geekosaur> k`` ^^
2024-05-01 19:54:10 +0200 <geekosaur> so yeh, it comes down to the ISA
2024-05-01 19:53:08 +0200Axma89310(~Axman6@user/axman6)
2024-05-01 19:53:03 +0200 <geekosaur> "Also, Intel's manual[1] states that the results are undefined when cnt is greater than the operand size, but at least for 32- and 64-bit data sizes it has been observed that shift operations are performed by (cnt mod n), with n being the data size."
2024-05-01 19:53:02 +0200Bynbo7(~Axman6@user/axman6) (Ping timeout: 244 seconds)
2024-05-01 19:52:46 +0200Axman6(~Axman6@user/axman6)
2024-05-01 19:52:21 +0200Axman6(~Axman6@user/axman6) (Ping timeout: 258 seconds)
2024-05-01 19:46:39 +0200 <gaff> lyxia: Not sure what you are saying there.
2024-05-01 19:45:06 +0200 <Franciman> ocaml's one is a pain sometimes
2024-05-01 19:44:53 +0200 <Franciman> i miss haskell's syntax T.T
2024-05-01 19:44:51 +0200 <geekosaur> (i.e. traps)
2024-05-01 19:44:35 +0200 <geekosaur> sorry, that'd be per bit. I wonder if some ISA simply rejects shifts > bitSize
2024-05-01 19:43:34 +0200 <lyxia> gaff: let m = EitherT (modify (+ 1) >> pure (Left ())) :: EitherT () (State Int) () in m *> m
2024-05-01 19:42:10 +0200 <lyxia> gaff: the second either always runs the two computations
2024-05-01 19:40:39 +0200euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de)
2024-05-01 19:40:22 +0200euleritian(~euleritia@dynamic-176-001-013-250.176.1.pool.telefonica.de) (Read error: Connection reset by peer)
2024-05-01 19:38:10 +0200 <geekosaur> I could also see it depending on ISA: whether shift-right is logical (0 shifts in) or arithmetic (carry bit shifts in)
2024-05-01 19:34:55 +0200hseg(~gesh@77.137.75.224) (Ping timeout: 246 seconds)
2024-05-01 19:34:53 +0200 <k``> (I assume that when it describes comparing things to `bitSize`, it means only for types where `bitSize` is a nonbottom, nonnegative value.)
2024-05-01 19:33:49 +0200 <geekosaur> also, signed vs. unsigned occurs to me as a potential problem, but I haven't looked to see if it's relevant
2024-05-01 19:33:49 +0200 <k``> It's not relevant to `Integer`.
2024-05-01 19:33:04 +0200 <geekosaur> whether it's meaningful depends on the type. consider `Integer`
2024-05-01 19:30:15 +0200euleritian(~euleritia@dynamic-176-001-013-250.176.1.pool.telefonica.de)
2024-05-01 19:29:52 +0200euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de) (Ping timeout: 255 seconds)
2024-05-01 19:29:18 +0200 <k``> Is there any particular reason that `Data.Bits.shiftR` is undefined for shifts greater than `bitSize`, but `Data.Bits.shiftL` is not?
2024-05-01 19:28:31 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl)
2024-05-01 19:28:27 +0200k``(~k``@152.1.137.158)
2024-05-01 19:26:24 +0200danza(~francesco@151.57.139.226) (Remote host closed the connection)
2024-05-01 19:25:35 +0200 <gaff> mauke: I am not clear why you are saying so. In any case, let us assume `m` is `StateT s Identity`.
2024-05-01 19:22:55 +0200 <mauke> gaff: I think it would depend on how >>= and <*> are defined for m
2024-05-01 19:20:51 +0200mima(~mmh@aftr-62-216-211-127.dynamic.mnet-online.de) (Ping timeout: 255 seconds)
2024-05-01 19:19:00 +0200danza(~francesco@151.57.139.226)
2024-05-01 19:16:22 +0200danza(~francesco@151.57.139.226) (Ping timeout: 255 seconds)
2024-05-01 19:09:42 +0200 <gaff> Appreciate any help.
2024-05-01 19:07:59 +0200 <hseg> Using stack with allow-newer, how can I get stack to dump the build plan it computed?
2024-05-01 19:07:32 +0200hseg(~gesh@77.137.75.224)
2024-05-01 19:05:38 +0200 <gaff> I have some code here https://goonlinetools.com/snapshot/code/#r7dkw4j84woahyak9mbns5 that has 2 ways to define Applicative instance for EitherT. I would like to know if there is any difference between the two definitions for <*>.
2024-05-01 19:05:32 +0200euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de)
2024-05-01 19:05:08 +0200euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de) (Read error: Connection reset by peer)
2024-05-01 19:04:55 +0200euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de)
2024-05-01 19:04:11 +0200euleritian(~euleritia@ip4d16fc38.dynamic.kabel-deutschland.de) (Remote host closed the connection)
2024-05-01 19:03:16 +0200gaff(~gaff@49.207.212.165)
2024-05-01 18:59:40 +0200danza(~francesco@151.57.139.226)
2024-05-01 18:56:00 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)