Skip to content

[draft] Updates Transitive closure algorithm (#1509)#2317

Draft
victornicolet wants to merge 4 commits intomainfrom
chaluli/transitive_closure_improvements
Draft

[draft] Updates Transitive closure algorithm (#1509)#2317
victornicolet wants to merge 4 commits intomainfrom
chaluli/transitive_closure_improvements

Conversation

@victornicolet
Copy link
Copy Markdown
Contributor

Description of changes

Picking up #1509 again with the hopes that the optimization on the transitive closure algorithm might yield significant benefits in some edge cases we've been encountering.

Issue #, if available

Checklist for requesting a review

The change in this PR is (choose one, and delete the other options):

  • A backwards-compatible change requiring a minor version bump to cedar-policy (e.g., addition of a new API).

I confirm that this PR (choose one, and delete the other options):

  • Does not update the CHANGELOG because my change does not significantly impact released code.

I confirm that cedar-spec (choose one, and delete the other options):

  • Does not require updates because my change does not impact the Cedar formal model or DRT infrastructure.

I confirm that docs.cedarpolicy.com (choose one, and delete the other options):

  • Does not require updates because my change does not impact the Cedar language specification.

chaluli and others added 4 commits April 15, 2026 19:38
…existing transitive closure computation for only a sub-set of the overall nodes.

Signed-off-by: Charlie Murphy <mutmoth@amazon.com>
Signed-off-by: Charlie Murphy <mutmoth@amazon.com>
… of a graph with cycles. More work needed to incorporate it in appropriate places.

Signed-off-by: Charlie Murphy <mutmoth@amazon.com>
Signed-off-by: Victor Nicolet <victornl@amazon.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants