Jan-Willem Maessen wrote:
I think that if I can get unsafeFreeze/unsafeThaw to work reliably,
it'll finally outperform Data.Map on your example. I haven't yet
played with the hash function, which looks kind of bad; there may be
hope for improvement there as well.
Great!
User-level Thaw
Sebastian Sylvan wrote:
On 11/8/05, Jan-Willem Maessen [EMAIL PROTECTED] wrote:
Just wanted to let people know that I've been working on improving
Data.HashTable, with the help of Ketil Malde's badly performing code
Always happy to help, of course - bad performance R us:-)
Request:
On Nov 9, 2005, at 4:46 AM, Ketil Malde wrote:
Sebastian Sylvan wrote:
On 11/8/05, Jan-Willem Maessen [EMAIL PROTECTED] wrote:
Just wanted to let people know that I've been working on improving
Data.HashTable, with the help of Ketil Malde's badly performing code
Always happy to help, of
On 11/9/05, Ketil Malde [EMAIL PROTECTED] wrote:
Sebastian Sylvan wrote:
On 11/8/05, Jan-Willem Maessen [EMAIL PROTECTED] wrote:
Just wanted to let people know that I've been working on improving
Data.HashTable, with the help of Ketil Malde's badly performing code
Always happy to
On Nov 7, 2005, at 9:02 AM, Bulat Ziganshin wrote:
...Simon, can you please write some docs about all these foreign stuff
and their interaction with pure Haskell code? i see some bits of this
information in these newsgroups regularly (for example, are you
remember discussion about using lots of
On 11/8/05, Jan-Willem Maessen [EMAIL PROTECTED] wrote:
On Nov 7, 2005, at 9:02 AM, Bulat Ziganshin wrote:
...Simon, can you please write some docs about all these foreign stuff
and their interaction with pure Haskell code? i see some bits of this
information in these newsgroups regularly
Hello Simon,
Monday, November 07, 2005, 4:16:54 PM, you wrote:
SM Yes, mallocForeignPtr's are implemented using pinned GC'd memory, with
SM no finalizer (unless you add one). That's why they're nice and fast.
Simon, can you please write some docs about all these foreign stuff
and their
