On Thu, Mar 24, 2011 at 12:12 AM, Ben Kloosterman <[email protected]>wrote:
> But I'm still reserving the possibility that vectors may need to be > chunked in order to support real-time collection. > > > > > > Why not push that GC intereaction to string , leave uString light weight. > If you really want to do it do it ..You may need to write a 64K string for > interop anyway. > I don't think I answered this. The model I'm really after here is that String should be the native string representation. Given the realization that chunking is not required on strings, that isn't really an issue. Also, given your 32K large heap observation, I'm now questioning whether chunking is necessary at all. 32K may not prove to be the right granularity, but the key point is that at some threshold you switch strategies for relocation. The choice of threshold is mostly about the amount of reference scanning you are willing to commit yourself to doing indivisibly. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
