Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You're describing a very intrusive garbage collector.

So, a weakly typed language with garbage collection? Where have we heard of that before?

I can imagine that if most of your code is for checking that the remaining fraction reads correctly from rvalues and writes correctly to lvalues and each check requires a round trip through a context switch, you're not going to be wringing very much productivity out of either your hardware as the CPU thrashes like mad or the one developer you manage to keep on staff.



Its not a garbage collector. All i want is to be able to query the list of allocation made by a process.

Performance would not need to be great, I would even assume it would be quite bad. But being able to write APIs, that have debug mode that tells you precisely when you give a API call broken pointers would be very useful.


The ability to know which memory is valid and which is garbage is indistinguishable from what a garbage collector does.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: