-
Notifications
You must be signed in to change notification settings - Fork 0
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
Proposed Method logic #2
Comments
Hey Irfaan, Case 1There are a few valid cases which will not be considered if we branch only when we hit the black hole. For example, consider this situation.
In this case, there could be a path where a being from the future influences the being in present time to get into the hole. Note that the being entering the hole in the first place is caused by the travelled being. If we branch only when someone hits the portal, we will miss this path.
Case 2Another reason this approach would fail is that once someone hits the portal, history has to rewritten. If rewritten, there is a chance that the being never hits the portal in the first place. So you'll have to update this by dropping a branch. This will happen back and forth resulting in an endless loop. Feel free to continue the argument if still unclear. |
Added explanation to readme |
Constructing tree of states for each possible next moves considering the possibility of time travel in the future seems inefficient and very memory hungry.
Depending on the theory/idea of time travel followed, it is possible that you can just have a main branch simulation, and then when time travel happens split it into multiple branches at the point of divergence time.
- Steins;Gate
Pretty similiar to tree only, but not all nodes will have splits
Are there any possible cases where this would not be sufficient?
The text was updated successfully, but these errors were encountered: