2024/05/01

Newest at the top

2024-05-01 20:35:56 +0200 <lambdabot> 0
2024-05-01 20:35:55 +0200 <k``> > shiftL 1 64 :: Word64
2024-05-01 20:34:23 +0200tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Quit: My iMac has gone to sleep. ZZZzzz…)
2024-05-01 20:33:53 +0200justsomeguy(~justsomeg@user/justsomeguy) (Quit: WeeChat 3.6)
2024-05-01 20:32:46 +0200 <k``> Oh wow. Looks like it's a documentation issue...
2024-05-01 20:30:54 +0200 <geekosaur> the docs look reversed for unsafeShiftR vs. shiftR (compare shiftL)
2024-05-01 20:30:52 +0200 <ncf> i knew he was never gonna let me down
2024-05-01 20:30:00 +0200danza(~francesco@151.19.252.90)
2024-05-01 20:29:58 +0200 <c_wraith> he's even released new stuff recently. and it's quite good.
2024-05-01 20:29:27 +0200 <monochrom> Rick Astley actually has his own youtube channel and posts his official MVs. I be damned.
2024-05-01 20:27:19 +0200mrmr1553343(~mrmr@user/mrmr)
2024-05-01 20:24:57 +0200 <k``> Seems like the processor issues make sense for `unsafeShiftR`, but maybe not `shiftR`. And the inconsistency between R and L is still unexplained...
2024-05-01 20:24:55 +0200 <dolio> Seconded.
2024-05-01 20:24:17 +0200 <probie> I think this is a better monad video https://www.youtube.com/watch?v=dQw4w9WgXcQ
2024-05-01 20:21:52 +0200mrmr1553343(~mrmr@user/mrmr) (Ping timeout: 256 seconds)
2024-05-01 20:20:48 +0200 <dolio> 15 minutes
2024-05-01 20:17:40 +0200 <monochrom> How long is it?
2024-05-01 20:13:20 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com)
2024-05-01 20:12:31 +0200 <ncf> i'm sure it's excellent since it starts with "the absolute best"
2024-05-01 20:11:29 +0200 <justsomeguy> What do you guys think of this monad video: https://www.youtube.com/watch?v=C2w45qRc3aU ?
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)