2025/03/26

Newest at the top

2025-03-26 04:37:36 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection)
2025-03-26 04:37:28 +0100bitdex_(~bitdex@gateway/tor-sasl/bitdex) bitdex
2025-03-26 04:37:03 +0100 <monochrom> -0 is as exact as +0.
2025-03-26 04:36:58 +0100 <monochrom> I interpret that asymmetry to mean "+0 is the default" not "there is no +0, instead a neutral 'exact' [sic] zero".
2025-03-26 04:36:57 +0100bitdex_(~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection)
2025-03-26 04:36:17 +0100 <monochrom> Sure, some asymmetry is inevitable.
2025-03-26 04:35:45 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) bitdex
2025-03-26 04:34:38 +0100bitdex_(~bitdex@gateway/tor-sasl/bitdex) bitdex
2025-03-26 04:34:37 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection)
2025-03-26 04:34:36 +0100 <haskellbridge> <Liamzee> thanks Axman6 , but ultimately I'd love to see Haskell's web-interfaces using linear haskell to reduce memory consumption and allocation time
2025-03-26 04:34:33 +0100 <geekosaur> the numerics folks demanded this behavior when IEEE floating point was being standardized
2025-03-26 04:33:24 +0100 <EvanR> if anything you just pointed out another (or instead of) asymmetry
2025-03-26 04:33:09 +0100 <haskellbridge> <Liamzee> thanks EvanR
2025-03-26 04:33:08 +0100 <geekosaur> this is related to numeric analysis and complex trig, and predates computers
2025-03-26 04:32:52 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 272 seconds)
2025-03-26 04:32:52 +0100 <lambdabot> arising from a use of ‘e_110505’
2025-03-26 04:32:52 +0100 <lambdabot> • No instance for (Fractional (Double -> Double))
2025-03-26 04:32:52 +0100 <lambdabot> error:
2025-03-26 04:32:50 +0100 <monochrom> > 1 / ((-0.5) + (+0.5))
2025-03-26 04:32:50 +0100 <EvanR> also +1 / +infinity = zero
2025-03-26 04:32:48 +0100 <geekosaur> go read that Oracle paper monochrom linked earlier
2025-03-26 04:32:21 +0100 <monochrom> Let me write very explicitly. (+1)/(+0) = +oo, (+1)/(-0) = -oo. That's btw another reason to keep a sign bit on zero.
2025-03-26 04:31:40 +0100 <EvanR> (or -zero)
2025-03-26 04:31:30 +0100 <EvanR> if you add -0.5 and +0.5, it equals zero, not +zero
2025-03-26 04:31:01 +0100 <monochrom> No, this is not about random or nondeterminism.
2025-03-26 04:30:43 +0100 <EvanR> none of*
2025-03-26 04:30:39 +0100 <EvanR> none this "every float is a random number around some point" crap xD
2025-03-26 04:30:27 +0100 <EvanR> sometimes it is exactly zero
2025-03-26 04:30:17 +0100 <monochrom> I would interpret the two signed zeros to be -0 and +0, rather than -0 and "neutral" 0.
2025-03-26 04:29:58 +0100 <EvanR> Liamzee, I see remoteHost :: SockAddr field in the Request type for wai
2025-03-26 04:29:12 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 268 seconds)
2025-03-26 04:28:43 +0100aetepe(~aetepe@188.119.22.83) (Ping timeout: 245 seconds)
2025-03-26 04:27:59 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-03-26 04:24:55 +0100 <geekosaur> but as I said earlier, I haven't messed with this since 1985, so…
2025-03-26 04:24:34 +0100aetepe(~aetepe@188.119.22.83) aetepe
2025-03-26 04:24:33 +0100 <geekosaur> and trig
2025-03-26 04:24:28 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-03-26 04:24:05 +0100 <geekosaur> yes. has to do with ranges
2025-03-26 04:23:51 +0100 <geekosaur> (I would have to read the spec to see if Report-compliant behavior or the extension is the correct behavior)
2025-03-26 04:23:22 +0100 <EvanR> zeroes in a quadrant
2025-03-26 04:22:33 +0100 <geekosaur> yes, and it exists solely to put zeroes in the correct quadrant on a plane
2025-03-26 04:22:03 +0100 <EvanR> so it's an asymmetric feature
2025-03-26 04:21:56 +0100 <EvanR> just noting there's no corresponding plus zero
2025-03-26 04:21:45 +0100 <geekosaur> monochrom posted an Oracle doc explaining it, beyond that I think the specification itself is probably the best source
2025-03-26 04:21:22 +0100 <haskellbridge> <Liamzee> if I want to pass the IP of the sender, how would I get warp / servant / twain to get the IP?
2025-03-26 04:21:18 +0100 <EvanR> I'm sure it is
2025-03-26 04:21:05 +0100 <geekosaur> EvanR, that behavior is specified by IEEE754
2025-03-26 04:21:04 +0100 <haskellbridge> <Liamzee> i'm building a rust-based microservices router, with the initial microservices being in Haskell
2025-03-26 04:20:38 +0100 <geekosaur> go ahead
2025-03-26 04:20:34 +0100random-jellyfish(~developer@user/random-jellyfish) (Ping timeout: 260 seconds)