> Much of the "overhead" of StablePtrs at the moment is due to > the hash table and reference count business that is > implicitly performed by the stable pointer routines. So > far, I haven't seen a good explanation as to why this is > actually needed. If we would get rid of it, StablePtrs > would be much more light weight. The hash table is there to ensure that if you make two StablePtrs for the same object, they will compare equal (see our paper on weak pointers etc.). This might not be necessary in some situations, so I agree we could have a lightweight version. Cheers, Simon
- RE: foreignObjToAddr Simon Marlow
- Re: foreignObjToAddr Sven Panne
- Re: foreignObjToAddr Manuel M. T. Chakravarty
- Re: foreignObjToAddr Marcin 'Qrczak' Kowalczyk
- Re: foreignObjToAddr Manuel M. T. Chakravarty
- RE: foreignObjToAddr Sigbjorn Finne
- RE: foreignObjToAddr Manuel M. T. Chakravarty
- Re: foreignObjToAddr Marcin 'Qrczak' Kowalczyk
- Re: foreignObjToAddr Sven Panne
- Marshalling in Haskell [was: Re: foreignObj... Manuel M. T. Chakravarty
- RE: foreignObjToAddr Simon Marlow
- RE: foreignObjToAddr Simon Marlow
- RE: foreignObjToAddr Sigbjorn Finne
- Re: foreignObjToAddr Marcin 'Qrczak' Kowalczyk
- Re: foreignObjToAddr Sven Panne
- Re: foreignObjToAddr Manuel M. T. Chakravarty
- Re: foreignObjToAddr Malcolm Wallace
- RE: foreignObjToAddr Simon Marlow
- RE: foreignObjToAddr Sigbjorn Finne
- Re: foreignObjToAddr Manuel M. T. Chakravarty
- Re: foreignObjToAddr Malcolm Wallace