DATAStack | 100 % Swift Simple Boilerplate Free Core Data Stack | iOS library

The problem is that your visitedStack keeps growing, as you are eventually pushing all nodes unto it. Be aware that all recursive executions of your function get the same visitedStack to work with. So pushing [...visitedStack] is not going to push a path, but all nodes that had been visited before, which after a while do not represent a path any more.

If we stick with your function, then just make sure you don't push on visited permanently, but create a copy of that stack with the extra node, which will remain in the deeper recursion, but will not contaminate the whole rest of the execution. This way that extra node will not be there in the other, sibling paths:

The problem you're seeing stems from the fact that you not haven't constrained the associate type WriterType within JsonProperties.

Currently, it accepts any WriterType type conforming to Writer, regardless of what its Model is.

What you probably want is for the WriterType type to have its Model be the same as the type being conformed to JsonProperties protocol - so you need to constrain it:

I also answered your question over at the CoreStore issues section.

There was a missing overload in the Where initializers which I'll add in an upcoming update, but you can also use the ~= operator as a shorthand syntax:

You will get an error, because your implementation of computeResult checks if the "commands"-list 'contains' these strings. And as the whole list DOES actually contain it, you try to pop items off the stack that don't exist.

So in short, the first if clause will already be executed and cause the error.

Try to debug your computeResult method.

The stack is empty because result isn't in yet. The issue is with your loadResults().