Fix degeneracy order and remove more clones #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
degeneracy_order
. It was doing the indexing-after-deleting thing, which was not correct. I think the tests were passing because the degeneracy order doesn't affect correctness (just speed).bron_kerbosch
. We could use eitherHashTrieSet
orVec
for the neighbourhoods. I'm not sure which is better, they seem about the same speed in testing, so usingVec
for now.attestation_pairwise_overlapping
test so that they pass. Another configuration that is feasible (but blows up badly) isnum_validators = 15 * spec.target_committee_size
withstep_size = 1
.compute_neighbourhood
function.