A while back, I had Swaroop add an INNER-REF operator in BitC. Given a
reference to a non-union aggregate, INNER-REF returns a pointer to some
member field. The intended use case had to do with some peculiar storage
allocators that used vectors of objects.
Subsequently, two things have become clear:
1. Inner-ref makes relocating collectors much less efficient.
2. The use case has turned out to be unmotivated, as there is never
a reason to iterate those allocation pools through the vector.
Lacking a use case, and in light of the GC problem, I now think that
INNER-REF was a mistake and should be removed.
Before we remove it, can anyone identify a compelling use-case for
INNER-REF?
shap
_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev
