Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compute characterization set returns empty set if automata is not minimal #38

Closed
icezyclon opened this issue Nov 11, 2022 · 5 comments
Closed

Comments

@icezyclon
Copy link
Contributor

The function compute_characterization_set on DeterministicAutomaton returns an empty list (set) if the provided automata is not minimal. This might lead to confusion, as an empty characterization set might actually exists, e.g., automata with 1 state, which cannot directly be differentiated from a "not minimal" automaton.

I would recommend returning None in the case that the automata is not minimal (or raising an Exception) instead of returning the empty set.

@emuskardin
Copy link
Member

Do I knooooooooooooooooooooow you? :p
Fixed :)

@emuskardin
Copy link
Member

emuskardin commented Nov 11, 2022

Knowing you, you will now request that == comparison between deterministic automata is enabled :p

Let me try doing that :p

@icezyclon
Copy link
Contributor Author

Do I knooooooooooooooooooooow you? :p Fixed :)

Did you also "fix" it in the tests? :P

Knowing you, you will now request that == comparison between deterministic automata is enabled :p

Let me try doing that :p

Sure ;)

@emuskardin
Copy link
Member

Test passed, I even checked as I could not live with embarrassment if this change (that you requested) did not pass on existing tests :)

And as you surely know, test cases that do not exist are also passing test cases.

@icezyclon
Copy link
Contributor Author

Test passed, I even checked as I could not live with embarrassment if this change (that you requested) did not pass on existing tests :)

And as you surely know, test cases that do not exist are also passing test cases.

You are right. As we know all(set()) == True 🥇 ;)

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

No branches or pull requests

2 participants