2025/03/25

Newest at the top

2025-03-26 00:30:26 +0100weary-traveler(~user@user/user363627) (Remote host closed the connection)
2025-03-26 00:27:21 +0100aetepe(~aetepe@188.119.22.83) aetepe
2025-03-26 00:26:38 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2025-03-26 00:25:48 +0100sarna(~sarna@d192-22.icpnet.pl) (Ping timeout: 245 seconds)
2025-03-26 00:25:18 +0100byte(~mu@user/byte) (Quit: Leaving)
2025-03-26 00:23:08 +0100__monty__(~toonn@user/toonn) (Quit: leaving)
2025-03-26 00:21:43 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-26 00:16:25 +0100 <geekosaur> last time I touched it was 1985
2025-03-26 00:15:39 +0100 <geekosaur> sadly it's been a looong time since I last did this stuff so it's all become kinda fuzzy ("use it or lose it")
2025-03-26 00:14:11 +0100 <otto_s> Yes.
2025-03-26 00:13:17 +0100 <otto_s> (and then late, of course, how log decides where to go)
2025-03-26 00:13:12 +0100 <geekosaur> right, but what I said is why the whole "negative zero" thing exists in the first place. see also atan2
2025-03-26 00:12:31 +0100 <lambdabot> True
2025-03-26 00:12:29 +0100 <otto_s> > isNegativeZero $ negate 0
2025-03-26 00:12:26 +0100 <otto_s> No, I think the culprit is just:
2025-03-26 00:11:26 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 268 seconds)
2025-03-26 00:10:43 +0100 <geekosaur> I think the full answer involves complex numbers as being on a plane, and having trig on them produce results in the correct quadrant?
2025-03-26 00:10:41 +0100 <otto_s> Floats are evil. *g*
2025-03-26 00:08:54 +0100 <otto_s> Oh, I see, mauke answered that already.
2025-03-26 00:06:16 +0100 <otto_s> Is there a reason, why the imaginary party of -1 :: Complex Double *should* be -0 ?
2025-03-26 00:06:04 +0100weary-traveler(~user@user/user363627) user363627
2025-03-26 00:05:56 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-26 00:05:44 +0100poscat(~poscat@user/poscat) poscat
2025-03-26 00:05:23 +0100poscat(~poscat@user/poscat) (Ping timeout: 245 seconds)
2025-03-26 00:03:22 +0100 <geekosaur> keep it but require `import IEEE754Insanity`
2025-03-25 23:59:54 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 272 seconds)
2025-03-25 23:58:54 +0100 <otto_s> Hehe.
2025-03-25 23:58:47 +0100 <mauke> petition to remove Double from the language
2025-03-25 23:58:26 +0100 <EvanR> float functions break congruence of function application
2025-03-25 23:57:46 +0100 <lambdabot> (True,False)
2025-03-25 23:57:44 +0100 <mauke> > let x = 0; y = -0 in (x == y, recip x == recip y)
2025-03-25 23:57:26 +0100 <EvanR> and decodeFloat is not the be all end all of the value
2025-03-25 23:57:22 +0100 <otto_s> Yes. :)
2025-03-25 23:57:16 +0100 <EvanR> mystery solved
2025-03-25 23:57:02 +0100 <lambdabot> False
2025-03-25 23:57:00 +0100 <otto_s> > isNegativeZero $ imagPart ((-1) :+ 0 :: Complex Double)
2025-03-25 23:56:56 +0100 <otto_s> isNegativeZero $ imagPart ((-1) :+ 0 :: Complex Double)
2025-03-25 23:56:40 +0100 <lambdabot> True
2025-03-25 23:56:39 +0100 <otto_s> > isNegativeZero $ imagPart (-1 :: Complex Double)
2025-03-25 23:56:29 +0100 <otto_s> Ah.
2025-03-25 23:56:20 +0100 <mauke> yes, so unary - negates both parts
2025-03-25 23:56:07 +0100 <mauke> hah
2025-03-25 23:56:02 +0100 <lambdabot> (-2.0) :+ (-3.0)
2025-03-25 23:56:01 +0100 <mauke> > negate (2 :+ 3)
2025-03-25 23:55:52 +0100 <EvanR> (.) . (.)
2025-03-25 23:55:36 +0100 <lambdabot> (0,0)
2025-03-25 23:55:35 +0100 <mauke> > owl
2025-03-25 23:55:25 +0100 <EvanR> that's the only thing I can think of
2025-03-25 23:55:12 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-03-25 23:55:08 +0100 <lambdabot> (0,0)