Equality checking when navigating back

[torresmi]

In the methods Navigator.goBackTo and Navigator.goBackBefore there are checks on the screen argument using structural equality (.equals()). The rest of the implementation uses referential equality.

Is it intentional to only allow for equal references in these methods? I have paths that are structurally equal but different references, so they won't work with these functions.

[ryanmoelter]

Thanks for reporting!

I'll have to put a little more thought into which version of equality we use, but regardless, we should be consistent across the library.

I'm guessing you would prefer structural equality everywhere?

[torresmi]

Sounds good! Consistency would be nice.

My preference would be structural equality so users don't have to manage references everywhere.