What's under the hood? [Ariel Weinstein]

re: What's under the hood? [Ariel Weinstein]

jgalla — Fri, 05 Aug 2005 20:49:03 GMT

My thoughts are that the documentation should include the algorithmic complexity of a particular operation. For example, I might not need to know exactly how a particular operation is performed, but I would like to know what the cost might be to use a particular function. There are many libraries (the C++ STL comes to mind) that does a fairly good job of providing such information.

re: What's under the hood? [Ariel Weinstein]

Dmitry — Fri, 05 Aug 2005 22:11:48 GMT

+1 to describe asymptotic behaviours for memory and speed.

Also could please describe the reasons for such a small set of collection classes?

re: What's under the hood? [Ariel Weinstein]

Milan Negovan — Sun, 07 Aug 2005 04:34:43 GMT

Collections are my biggest pet peeve with .NET. :) I've posted my views on collections at http://aspnetresources.com/blog/dotnet_collection_madness.aspx and http://aspnetresources.com/blog/dotnet_collection_madness2.aspx.

re: What's under the hood? [Ariel Weinstein]

Michael Vanhoutte — Mon, 08 Aug 2005 22:26:35 GMT

I agree with jgalla. Often I want to have an idea of the algorithm used internally, not because I really want to know how it works, but because I want to have an idea of how fast a particular method works. Since most of these algorithms are not documented, I currently use reflector to learn what I want to know.

re: What's under the hood? [Ariel Weinstein]

Geoff Van Brunt — Mon, 08 Aug 2005 23:32:37 GMT

I agree, I often have to come up with a working solution just to test the performance of a collection/etc because there is no documentation on performance/algorithms are used. I've sometimes used reflector to dig through the code to figure out what is going on. Either way, not a fast way of gleening this information.

Idea: Indexes in .NET BCL 3.0 Collections

notgartner.com: Mitch Denny's Blog — Wed, 10 Aug 2005 02:05:59 GMT

Suggestions

Brien — Sat, 20 Aug 2005 15:27:48 GMT

Cool Ideas for the Collections API:

1. A performant dictionary that maintains insertion order (*cough* java.util.LinkedHashMap *cough*).
2. A performant dictionary that maintains sort order (*cough* java.util.TreeMap *cough*).