Top 5

[Christopher Wright]

Chris R. Miller wrote:
> dsimcha wrote:
>> 2.  Less conservative GC.  It's aggravating when a supposedly GC'd 
>> language for
>> all practical purposes still requires manual deallocation of some 
>> stuff if you're
>> working with large datasets, due to false pointer issues.
> 
> I am curious, what is the feasability of writing a garbage collector 
> where you could change the conservativsy at run-time?  (Perhaps stupid 
> to ask, but I never know 'till I ask).

This is an issue of RTTI granularity. Since there is no significant 
speed benefit from using a less conservative GC, there is never a reason 
to prefer a less conservative GC. Therefore your GC should always be as 
precise as the type information allows.