Timeline for "Sack" data structure in C#
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Dec 16, 2019 at 7:40 | history | suggested | marco sussitz | CC BY-SA 4.0 |
Removed introductory phrase and fixed typo
|
| Dec 16, 2019 at 7:25 | review | Suggested edits | |||
| S Dec 16, 2019 at 7:40 | |||||
| Dec 16, 2019 at 1:22 | comment | added | Zac Faragher | Worth noting that the comment about instances of Random created close together using the same seed only applies to .Net Framework. .Net Core uses a dedicated RNG instance to seed each new Random() instance, so the seed will be different. Source Code, Stack Overflow Question | |
| Dec 16, 2019 at 0:44 | comment | added | Rob |
If objects is private, readonly and cannot be injected into Sack, there's no benefit to be had by coding against IList<T> rather than List<T>.
|
|
| Dec 15, 2019 at 5:49 | comment | added | corsiKa |
It seems a Count property would be in order as well - most collections-esque tend to have it
|
|
| Dec 14, 2019 at 12:30 | comment | added | Heslacher |
I would use an overloaded method which takes a Type and then I would remove all objects of this Type.
|
|
| Dec 14, 2019 at 12:14 | comment | added | Al2110 |
What if I want to provide the option of emptying the contents to a specific collection, rather than just clearing it? Provide an overload for Empty() so that the data structure can be passed into it?
|
|
| Dec 14, 2019 at 12:04 | history | answered | Heslacher | CC BY-SA 4.0 |