| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
| |
Files which are installed as-is (any .service and other unit files, .conf
files, .policy files, etc), are left as is. My assumption is that SPDX
identifiers are not yet that well known, so it's better to retain the
extended header to avoid any doubt.
I also kept any copyright lines. We can probably remove them, but it'd nice to
obtain explicit acks from all involved authors before doing that.
|
| | |
|
| | |
|
| |
|
|
|
| |
test-hashmap is a very good test, but it gets in the way when one wants to
compile and quickly test changes.
|
| | |
|
| | |
|
| |
|
|
|
| |
Check string ops hashmap_put() for keys with a different pointer but the same
value.
|
| |
|
|
|
|
| |
Check return value of hashmap_ensure_allocated().
CID#1250807.
|
| | |
|
| | |
|
| |
|
|
| |
A reimplementation of hashmaps will follow and it will use 0.8.
|
| |
|
|
|
|
| |
It cannot fail in the current hashmap implementation, but it may fail in
alternative implementations (unless a sufficiently large reservation has
been placed beforehand).
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Test more corner cases and error states in several tests.
Add new tests for:
hashmap_move
hashmap_remove
hashmap_remove2
hashmap_remove_value
hashmap_remove_and_replace
hashmap_get2
hashmap_first
In test_hashmap_many additionally test with an intentionally bad hash
function.
|
|
|
test-hashmap-ordered.c is generated from test-hashmap-plain.c simply by
substituting "ordered_hashmap" for "hashmap" etc.
In the cases where tests rely on the order of entries, a distinction
between plain and ordered hashmaps is made using the ORDERED macro,
which is defined only for test-hashmap-ordered.c.
|
