Opportunity

[Timon Gehr]

On 04/10/2013 05:57 AM, Walter Bright wrote:
> On 4/9/2013 1:17 AM, Russel Winder wrote:
>> I have yet to find anyone who can tell me why Go must have generics with
>> a cogent argument that makes sense to me.
>
> ....
> What this means is the compiler (and language) needs NO KNOWLEDGE of
> what the GC needs. The library implementer is free to innovate whatever
> kind of tables are necessary. It means that radically different GCs can
> be built and swapped in and out without change to the compiler or
> language. It means that anyone who wants to build a better GC can do so
> without forking the compiler.

What about precise tracking of stack references?