2025/02/08

Newest at the top

2025-02-08 05:16:37 +0100cheater_cheater
2025-02-08 05:16:33 +0100cheater(~Username@user/cheater) (Ping timeout: 265 seconds)
2025-02-08 05:13:00 +0100cheater_(~Username@user/cheater) cheater
2025-02-08 05:11:25 +0100remedan(~remedan@ip-62-245-108-153.bb.vodafone.cz) remedan
2025-02-08 05:07:16 +0100remedan(~remedan@ip-62-245-108-153.bb.vodafone.cz) (Quit: Bye!)
2025-02-08 05:04:52 +0100Jeanne-Kamikaze(~Jeanne-Ka@c-73-93-78-113.hsd1.ca.comcast.net) (Quit: Leaving)
2025-02-08 05:03:15 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 268 seconds)
2025-02-08 04:58:37 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-08 04:54:49 +0100remedan(~remedan@ip-62-245-108-153.bb.vodafone.cz) remedan
2025-02-08 04:52:23 +0100MyNetAz(~MyNetAz@user/MyNetAz) MyNetAz
2025-02-08 04:51:10 +0100remedan(~remedan@ip-62-245-108-153.bb.vodafone.cz) (Quit: Bye!)
2025-02-08 04:46:36 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 268 seconds)
2025-02-08 04:45:23 +0100MyNetAz(~MyNetAz@user/MyNetAz) (Remote host closed the connection)
2025-02-08 04:36:58 +0100remedan(~remedan@ip-62-245-108-153.bb.vodafone.cz) remedan
2025-02-08 04:35:26 +0100 <monochrom> (And also a pointer to the 3*f(2) so I don't have to search in the future when I'm ready for it. And so on so forth.)
2025-02-08 04:34:42 +0100remedan(~remedan@ip-62-245-108-153.bb.vodafone.cz) (Quit: Bye!)
2025-02-08 04:30:50 +0100 <monochrom> If I don't have a stack, I just have to scan the long expression "5 * (4 * (3 * f(2)))" for the redex, f(2). This is slow, but I don't need a stack. A stack is there to save a pointer to the f(2) subexpr so I don't have to search.
2025-02-08 04:29:27 +0100 <monochrom> A functional example goes like this. To execute f(5), it goes: f(5) -> 5 * f(4) -> 5 * (4 * f(3)) -> 5 * (4 * (3 * f(2))) -> ...
2025-02-08 04:27:58 +0100 <monochrom> Equally well. I never assumed a fixed number.
2025-02-08 04:27:29 +0100 <geekosaur> how well does that work for a non-fixed number of calls?
2025-02-08 04:21:42 +0100 <monochrom> (It is still not O(1) space. Every procedure call becomes an inline expansion of the procedure text.)
2025-02-08 04:19:08 +0100 <monochrom> Because if you don't mind a quadratic slowdown, you don't need a stack.
2025-02-08 04:18:43 +0100 <monochrom> Have they gone one step further and go "and the stack is just an optimization"?
2025-02-08 04:18:02 +0100 <c_wraith> I have absolutely seen some people go "oh, it's just using a stack" and never have an issue with it again.
2025-02-08 04:17:08 +0100 <monochrom> I even go as far as making this joke. (Context: Everyone except me teach recursion by teaching how to execute by hand.) Your computer has been executing recursion for years. Has it learned anything yet?
2025-02-08 04:16:42 +0100 <c_wraith> for some people, yes.
2025-02-08 04:15:58 +0100 <monochrom> c_wraith: I am arrogant, I say that I am sure recursion is not more easily learned by see how to compile. In fact, has anything been made easier to learn by seeing how to compile it?
2025-02-08 04:15:48 +0100fmira(~user@user/fmira) (Ping timeout: 264 seconds)
2025-02-08 04:13:18 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 268 seconds)
2025-02-08 04:09:53 +0100vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2025-02-08 04:08:52 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-08 04:08:22 +0100vanishingideal(~vanishing@user/vanishingideal) (Ping timeout: 268 seconds)
2025-02-08 04:04:14 +0100Guest42(~Guest42@220-233-36-23.ip4.exetel.com.au) (Client Quit)
2025-02-08 04:02:53 +0100Guest42(~Guest42@220-233-36-23.ip4.exetel.com.au)
2025-02-08 04:00:55 +0100tavare(~tavare@user/tavare) tavare
2025-02-08 04:00:55 +0100tavare(~tavare@150.129.88.189) (Changing host)
2025-02-08 04:00:55 +0100tavare(~tavare@150.129.88.189)
2025-02-08 04:00:42 +0100aaronv(~aaronv@user/aaronv) aaronv
2025-02-08 04:00:17 +0100aaronv(~aaronv@user/aaronv) (Remote host closed the connection)
2025-02-08 03:53:57 +0100aaronv(~aaronv@user/aaronv) aaronv
2025-02-08 03:53:33 +0100aaronv(~aaronv@user/aaronv) (Remote host closed the connection)
2025-02-08 03:49:58 +0100cheater(~Username@user/cheater) cheater
2025-02-08 03:41:34 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-02-08 03:40:13 +0100ColinRobinson(~juan@user/JuanDaugherty) (Quit: praxis.meansofproduction.biz (juan@acm.org))
2025-02-08 03:38:24 +0100erdem(~erdem@user/erdem) erdem
2025-02-08 03:30:06 +0100xff0x(~xff0x@2405:6580:b080:900:a44a:d727:8d11:d274)
2025-02-08 03:29:51 +0100emergence7emergence
2025-02-08 03:29:51 +0100emergence(emergence@vm0.max-p.me) (Read error: Connection reset by peer)
2025-02-08 03:29:32 +0100emergence7(emergence@vm0.max-p.me) emergence
2025-02-08 03:28:53 +0100Jeanne-Kamikaze(~Jeanne-Ka@c-73-93-78-113.hsd1.ca.comcast.net) Jeanne-Kamikaze