Libfa: expose more FA operations to public #867
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ssible; expose clone, determinize, add_state, add_trans to public for flexible external uses
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
To enable more flexible uses of libfa, I exposed the following functions to public:
fa_clonefa_determinize(new wrapper arounddeterminize)fa_add_state(originallyadd_state)fa_add_new_trans(originallyadd_new_trans)Also, I added "const" qualifiers to parameters in most exposed functions where the FA is not modified.
Why I introduce this change: Libfa was modified like so and used by our work RELIA: Accelerating the Analysis of Cloud Access Control Policies in ASE 2025 conference. I think with more FA operations exposed, it would help researchers and developers to do more amazing things around this fast FA library.