-
Updated
Oct 14, 2020 - Go
red-black-tree
Here are 212 public repositories matching this topic...
-
Updated
Oct 14, 2020 - C#
-
Updated
Jan 21, 2018 - C
-
Updated
Oct 17, 2020 - TypeScript
-
Updated
May 21, 2019 - TypeScript
-
Updated
Oct 16, 2020 - C++
-
Updated
Jan 17, 2020 - Solidity
-
Updated
May 29, 2020 - C
-
Updated
Nov 24, 2017 - Lua
-
Updated
Nov 24, 2017 - C#
-
Updated
Feb 2, 2018 - Java
-
Updated
Feb 28, 2020 - C
-
Updated
Feb 6, 2019 - Fortran
-
Updated
Sep 17, 2019 - C++
-
Updated
Oct 4, 2020 - C++
-
Updated
Jan 21, 2017 - C#
-
Updated
Jul 27, 2019 - C++
-
Updated
Oct 1, 2020 - C++
-
Updated
Dec 5, 2017 - Java
-
Updated
Aug 6, 2020 - C++
-
Updated
Jun 7, 2020 - C
-
Updated
Sep 29, 2020 - Haskell
-
Updated
Sep 4, 2018 - Go
-
Updated
Jan 14, 2019 - C++
-
Updated
Aug 5, 2019 - C
-
Updated
May 29, 2019 - Rust
-
Updated
Nov 25, 2019 - Python
-
Updated
Jul 16, 2020 - JavaScript
-
Updated
Apr 6, 2019 - Go
Improve this page
Add a description, image, and links to the red-black-tree topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the red-black-tree topic, visit your repo's landing page and select "manage topics."


alloc/free are big performance killers in the persistent tree. it could be very beneficial to use a object pool in the implementation, at least as an option.