-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
Add NFA Simulator hole #1036
Comments
Every DFA is also an NFA. We can support contravariance here: every NFA Simulator solution should be a DFA Simulator solution. Example input
Example output
We can also use |
I don't think DFA simulator is popular enough to justify adding related holes that are similar. |
From SirBogman here
|
I am happy to update the arrow and empty set symbol to > and {}. I will ponder adding the S. I think there is an argument to be made that one of the interesting parts of DFA was to identify the correct next row. Adding this simplification has merit for this variant. |
Seconding the call for a switch from → to >, I think the hole should mimic the DFA hole as much as possible. I personally don't feel the need for the S, the info is all found consistent distances after the newline, and the DFA hole didn't have it. I don't mind the ∅ much either way, the solution would be a little shorter and cleaner without it but it's not an unreasonable edge case to handle and it looks pretty. Wasn't an issue in terms of the actual text processing, but for aesthetics I'd prefer if the table looked a little neater by padding the columns out to line up.
or
and just for good measure, a wild, out there proposal that because the states are one-digit numbers, the set notation is not strictly necessary
neither are the dividers
and for maximal minimalism
this would declutter the screen and make it look more similar to the DFA hole, but at the expense of some clarity. and who doesn't love brackets? So i think there's good cases to be made for many setups. But I had fun solving it and I think it's a good hole. edit: didn't realize btnlq basically proposed option 4 already, my main point is the columns should line up. |
Collaboration with @msbranicky
by popularish demand...
we bring you Finite Automaton Chapter II
Description
See https://github.com/code-golf/code-golf/pull/1037/files
Example input (if any)
Example output
The text was updated successfully, but these errors were encountered: