# | User | Rating |
---|---|---|
1 | tourist | 3985 |
2 | jiangly | 3814 |
3 | jqdai0815 | 3682 |
4 | Benq | 3529 |
5 | orzdevinwang | 3526 |
6 | ksun48 | 3517 |
7 | Radewoosh | 3410 |
8 | hos.lyric | 3399 |
9 | ecnerwala | 3392 |
9 | Um_nik | 3392 |
# | User | Contrib. |
---|---|---|
1 | cry | 169 |
2 | maomao90 | 162 |
2 | Um_nik | 162 |
4 | atcoder_official | 161 |
5 | djm03178 | 158 |
6 | -is-this-fft- | 157 |
7 | adamant | 155 |
8 | awoo | 154 |
8 | Dominater069 | 154 |
10 | luogu_official | 150 |
Name |
---|
Auto comment: topic has been translated by adamant (original revision, translated revision, compare)
It is a great proposal but I don't think that it will be a successful one. The standard is kept as clear and simple as possible so adding a lot of data structures might break this idea.
STL should be useful, not simple.
That's wrong on many levels. Every single piece of code in the C++ standard must be maintainable and possibly upgradable (see move semantics for example). It is very hard to maintain a large number of containers so don't expect any new data structure in the near future (there are much more useful containers like
dynarray
which are not ready yet so I don't expect to see tries any time soon)Absolutely agree!!!
The find_by_order() and order_of_key() should be added to set, map. I do not want to make a long declaration to have exactly the same set structure with only two more functionality.
And I don't want to spend precious processor time to update counters I'll never use if I don't use find-by-order or orderofkey