> I'm not sure what the use case for the recursive "is" is, but it would be > no cheaper than "==" in that case. I'm disinclined to change things. I can understand why you might be disinclined, but I do see why recursive "is" might be cheaper. The simplest case is probably comparing two 2-element tuples, where the elements are arbitrary objects. == might not even be defined on those objects, but "is" would be.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4