1a5b12aa5d
if we're doing a find/insert on a set or a map, it is better to just do a conditional insert/emplace operation than triggering two lookups. Change-Id: I80da5097f5a89fe30fa348ce5b6e747c34287a8d Reviewed-on: https://gerrit.libreoffice.org/70937 Tested-by: Jenkins Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk> |
||
|---|---|---|
| .. | ||
| inc | ||
| source | ||
| test | ||
| tools | ||
| CustomTarget_regcompare_test.mk | ||
| Executable_regmerge.mk | ||
| Executable_regview.mk | ||
| IwyuFilter_registry.yaml | ||
| Library_reg.mk | ||
| Makefile | ||
| Module_registry.mk | ||
| README | ||
| StaticLibrary_registry_helper.mk | ||
Registry reading, etc. This provides tools for dealing with the legacy binary types database format, still in use by extensions and the core code. While the actual binary file format is implemented by the [[store]] code, the wrapper that turns this into a type registry is implemented here. While this code is primarily used in only two modes: * linear write / concatenate * random access read The API unfortunately exposes a random-access write approach, which - while ~unused needs before we can re-write this away from the store backend.