3 ms·
It does not count under private memory, so I assume mapped but unused. The last time I asked Claude, it said confidently it was a bug in Swift's networking stac
by atombender 9mo ago
It does not count under private memory, so I assume mapped but unused. The last time I asked Claude, it said confidently it was a bug in Swift's networking stack, which I doubt.
- DrewADesign 9mo agoThat’s the great thing about indiscriminately scraping the internet for knowledge. I’ll bet Claude was channeling some Reddit guru dripping with swagger born from knowing their understanding of coding is far more advanced than most big-shots in the field— especially impressive because they only wandered into /r/LearnProgramming for the first time several months prior.
- stavros 9mo agoThis guru's comment probably started with "I'll bet" too.
- DrewADesign 9mo agoI see what you did there.
- piperswe 9mo agoMapped but unused memory is imaginary (at least, on modern UNIX systems). It's not actually using any physical RAM.
- junon 9mo agoWell, depends. Not always zero but in a good implementation not more than a few bytes per allocation, at most (if not zero).
- atombender 9mo agoThat is true, but I don't see other applications consuming ever-increasing amounts of virtual memory, so to me it suggests a bug.
- saagarjha 9mo agoSwift does not really have a networking stack
- codr7 9mo agoI've been out of the feature factory loop for a little while, but something tells me reviewing PRs is more entertaining these days.