-
Notifications
You must be signed in to change notification settings - Fork 3
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
Branching split up into several steps #3
Comments
The |
Depending on the design planned, relying on two functions for left and right node prohibits from non-binary branching. |
Yeah the plan was to make that a default maybe but have the ability to do as many nodes as you wish. |
the argument against would be that the interface to implement becomes |
Oh yeah I overlooked that that getting the branching variable could also be different. |
Currently
branch!
is a single function I think it makes sense to split it up into:get_branching_variable
branch_on_variable
or even
get_branching_variable
get_left_node
get_right_node
maybe also a combination of the two is possible.
By calling the lower one as a default but allowing the way like this:
this way there is a possibility to have more than two children easily.
The text was updated successfully, but these errors were encountered: