-
Notifications
You must be signed in to change notification settings - Fork 13
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
num_of_states()
is both in nfa and delta
#340
Comments
No, it is not correct. In the newest iteration of delta design, |
It is a bit confusing to have two functions |
I do not understand. They return the same thing. Number of states in I would have no problem with renaming |
In |
I am not sure how to rename it, maybe |
This is the intended behaviour. I do not see a problem here, but I understand what you mean by causing confusion now. You either type I personally consider this to be understandable and it does not confuse me. I cannot think of any other reasonable name, either. If we have an idea, I would be open to renaming the method in |
It's just a bit weird to ask for number of states in delta, it could look like it is the same thing as for nfa, but yeah, let's just keep it, you can close this issue. |
We will see whether someone will think of a better name. Anyone else any opinions or ideas? |
What about something like |
@kilohsakul Any opinions? |
Nfa's
num_of_states()
returns themaximum(max_initial, max_final, delta.num_of_states())
.Delta's
num_of_states
returns the number of sources (is this correct? will it also count the targets?).We should probably rename delta's function.
The text was updated successfully, but these errors were encountered: