On Fri, Sep 10, 2010 at 8:49 AM, Isaac Gouy <igo...@yahoo.com> wrote: >> Huh ? point ? it was just a casual comment, no point was intended. And >> I have read some comments by Don that what is in the shoutout is way >> faster than Data.HashTable > > > If you knew there was another option why write "I doubt there is any > choice for Haskell" ?
That was referring to the original comment about 'making a mutable implementation' meaning the program itself ASKED for that particular functionality. The one in the shoutout is one implementation of it, the one in Data.HashTable is another. When I said no choice, I was saying no choice but to implement a mutable hash table, in respond to the underlying message of 'why did they implement a mutable hashtable' as if making it mutable is only for performance purpose. > > >> >> And Data.HashTable also use some mutable array thing so it is still not >> >> the idiomatic Haskell of everything is immutable. >> >> > afaict idiomatic is everything referentially transparent not >> > everything immutable, as in - "I needed a halfway decent mutable >> > collection type – having a properly tested mutable collection that >> > actually performs well would be a godsend." >> >> how can you assure that(let's put aside the under the hood things >> where it is done in C) if you break the assumption that value can be >> changed. > > > Reading the first paragraph "Introduction to Uniqueness Typing" of > this paper should help you with that question - > > http://www.st.cs.ru.nl/papers/2008/vrie08-IFL07-UniquenessTypingSimplified.pdf > > Would try to digest that. > I'm not going to speculate about what unnamed "verteran Haskellers" > have or have not said. > > Read the bug report and you'll see that the root problem was GC - do > you think changing GC is a quick fix? > Don suggested on reddit for some fixes that tackle the GC issue(not changing the GC, but the way to get around the performance caused by GC), using similar approach as in the shoutout. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
