From a42067fa95c6abda2d527aebf736d67c29e72f62 Mon Sep 17 00:00:00 2001 From: Lukas Tenbrink Date: Wed, 28 May 2025 12:22:28 +0200 Subject: [PATCH] Remove `VMap` from c++ data types. --- contributing/development/cpp_usage_guidelines.rst | 4 ---- 1 file changed, 4 deletions(-) diff --git a/contributing/development/cpp_usage_guidelines.rst b/contributing/development/cpp_usage_guidelines.rst index 02e38a1bf..1f96ecc35 100644 --- a/contributing/development/cpp_usage_guidelines.rst +++ b/contributing/development/cpp_usage_guidelines.rst @@ -115,10 +115,6 @@ scripting API. | ``RBMap`` | ``std::map`` | Uses a `red-black tree `__ | | | | for faster access. | +------------------------+--------------------------+---------------------------------------------------------------------------------------+ -| ``VMap`` | ``std::flat_map`` | Uses copy-on-write (COW) semantics. | -| | | This means it's generally slower but can be copied around almost for free. | -| | | The performance benefits of ``VMap`` aren't established, so prefer using other types. | -+------------------------+--------------------------+---------------------------------------------------------------------------------------+ | ``Dictionary`` 📜 | ``std::unordered_map`` | Keys and values can be of any Variant type. No static typing is imposed. | | | | Uses shared reference counting, similar to ``std::shared_ptr``. | | | | Preserves insertion order. Uses ``HashMap`` internally. |