Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Original:
I refreshed my memory on Go Interfaces and it seems like it pretty much comes down to if you define an interface function on a reference then that interface only applies to the pointer type. However if you define the function on a value then the interface applies to both reference and value types.
What I suspect happened previously is that there was some code that relied on the false assumption that Stacks could be values on another Stack and this was breaking things. That doesn't really make any sense and is why the value type cases were removed in this PR as well.
See also: