You must contribute so much.
Haskell programming language
Samuel James
Robert Perry
okay rat. more c fags that think they are the only ones that can do pointer arithmetic. it is simply impossible to manipulate the hardware in anything other than c.
Dominic Jenkins
...
Austin Perry
you sure know a lot about java user
Nathan Ward
I know a lot about everything, qt. I actually program.
Jonathan Edwards
Just make sure to wash your hands before using the computer Aditya then you can continue your Java allocator work.
Mason Barnes
How did you even manage to finish typing this?
Who gives a shit what the language thinks?
On the many subjects of human error, languages are either helpful or not. Mostly, they're not.
Hunter Thomas
Is it that hard to process? Memory clogs are a significantly different class of error. It's an error that the language cannot tell is an error, and thus static analysis cannot tell is an error, and thus runtime analysis cannot tell is an error, but can be corrected at any time during execution by a sufficiently capable language (many safety-critical languages have facilities that can be used for that purpose).
It's impressively stupid to try to roll that up with memory leaks, which are errors according to the language, and thus can often be detected by static analysis, and thus can often be detected by runtime analysis, but might become uncorrectable by any means during execution.
Memory leaks are a systemic failure, not just a decision made by the human that is later considered to be a mistake. As such, they are far more dangerous and warrant care to avoid. They're also worth designing automated tools to identify, and doing research on finding the best methods of detection and avoidance. There's no point to doing research on memory clogs as their cause is your programmer is a slob. No automated tool can save them from being a slob. The only tools in this space are heap visualizers which assume your slob is too slovenly to notice a problem without a visualizer rubbing their nose in it until they decide to change.
Xavier Martinez
This is incorrect. Imagine this scenario. When a user connects to the system a user object is created. When the user disconnects this user object should turn into garbage. You can prove that this happens by showing that all the references to it have been removed. I don't get why you think it is impossible. These """clogs""" happen when an object does not turn into garbage at the end of its desired lifetime.