Open ctjoreilly opened 8 years ago
For now, I would not recommend tackling this as I'd really like to get the basic probability logic in place in the AIMA4e branch first, which I don't want to be a direct copy of the AIMA3e version as I'd like to improve upon it first.
Would you be able to loop back to the BidirectionalSearch and look at updating the API to support something like this:
interface BidirectionalActions {
List<A> fromInitialStatePart()
List<A> fromGoalStatePart()
List<A> fromInitialStateToGoalState(); // What I was indicating above I was expecting as a result
List<A> fromGoalStateToInitialState(); // essential the reverse of the previous method.
}
as the return from SearchForActionsBidirectionallyFunction and update the tests accordingly. That would, in my mind, stabilize the API and let @globalworming move forward with his alternative implementation approaches.
@ctjoreilly
Ya i get your point. I will come up with a way for such an implementation to BidirectionalSearch.
@ctjoreilly It would be really helpful if you could make an issue for the same, so that we can have a medium for discussions. Thanks.
May I start working on this issue? @ctjoreilly