Staging
v0.8.1
v0.8.1
https://github.com/python/cpython
Revision a43fea88577c460eed7cc92a37b5fce787d6aab1 authored by dependabot[bot] on 01 December 2020, 14:59:12 UTC, committed by GitHub on 01 December 2020, 14:59:12 UTC
Bumps [actions/cache](https://github.com/actions/cache) from v2.1.2 to v2.1.3. - [Release notes](https://github.com/actions/cache/releases) - [Commits](https://github.com/actions/cache/compare/v2.1.2...0781355a23dac32fd3bac414512f4b903437991a) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
1 parent bc662c0
Tip revision: a43fea88577c460eed7cc92a37b5fce787d6aab1 authored by dependabot[bot] on 01 December 2020, 14:59:12 UTC
build(deps): bump actions/cache from v2.1.2 to v2.1.3 (23582)
build(deps): bump actions/cache from v2.1.2 to v2.1.3 (23582)
Tip revision: a43fea8
rotatingtree.h
/* "Rotating trees" (Armin Rigo)
*
* Google "splay trees" for the general idea.
*
* It's a dict-like data structure that works best when accesses are not
* random, but follow a strong pattern. The one implemented here is for
* access patterns where the same small set of keys is looked up over
* and over again, and this set of keys evolves slowly over time.
*/
#include <stdlib.h>
#define EMPTY_ROTATING_TREE ((rotating_node_t *)NULL)
typedef struct rotating_node_s rotating_node_t;
typedef int (*rotating_tree_enum_fn) (rotating_node_t *node, void *arg);
struct rotating_node_s {
void *key;
rotating_node_t *left;
rotating_node_t *right;
};
void RotatingTree_Add(rotating_node_t **root, rotating_node_t *node);
rotating_node_t* RotatingTree_Get(rotating_node_t **root, void *key);
int RotatingTree_Enum(rotating_node_t *root, rotating_tree_enum_fn enumfn,
void *arg);
Computing file changes ...