Missing nodes on when calling Depthfirst.Traverse.PostOrder about treelib HOT 2 CLOSED

Hi, I've seen this problem in my unit tests before just never got around to actually fixing it :-( but the good new is that I think I fixed it now :-)

The fixed solution is in a seperate branch: Depthfirst.Traverse.PostOrder

• Would you be able to test this for me and let me know if you see any issues with it?

I found that the old traversal structure was not too useful here because it had no direct readable states towards whether:

• a node has been visited
• a nodes children have been visited and so forth

So, I redesigned the algorithm using the private utility class:
TreeLib.Depthfirst.Traverse.VisitElement<T>

This class allows me tho keep the state in very simple way and yield each node in a simple while loop as you can see in the static IEnumerable<T>PostOrderIterator<T>(...) method in TreeLib.Depthfirst.Traverse.

The case you are reporting is this:

This structure is tested in a unit test in TreeLibNugetUnitTests.CoreTests.TestMethod8() and does no longer return an error. I have added one or 2 more unit tests here for good measure but I think this is fine. Would you want to add more test patterns? If so, please let me know also...

Thanks for your detailed feedback.

from treelib.

First of all thanks for your quick response.So after a brief testing everything seems to work correctly.If i find something else i will keep you posted.Thanks!

from treelib.