<div dir="ltr">I'm curious: why do you want all characters to be eq? to each other instead of just equal??<div><br></div><div>Robby</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, May 4, 2013 at 10:57 AM, Jon Zeppieri <span dir="ltr"><<a href="mailto:zeppieri@gmail.com" target="_blank">zeppieri@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Since incompatible future changes seem to be coming up a lot, I<br>
thought I'd add one more. What do the members of this list think of<br>
removing eqv? all of its associated machinery (e.g., memv, hasheqv,<br>
etc.)?<br>
<br>
(Along with this change, it would be nice if characters could all be<br>
immediately represented, so that those with equal code points would be<br>
eq? RIght now, all unicode code points can be encoded in 22 bits, I<br>
think. I'm not so familiar with racket's current representation of<br>
characters, but I figure that they could easily be fit into a single<br>
machine word on 64-bit builds. I don't know how difficult it would be<br>
on 32-bit builds. And, of course, there's no guarantee that the number<br>
of code points won't increase significantly.)<br>
<br>
Alternatively (and following Sam's line of thought from [1]), eqv?<br>
could be extended to cover all of racket's immutable data structures.<br>
In this case eqv? should also be made generic so that user-defined<br>
immutable data structures can use it, as well.<br>
<br>
<br>
[1] <a href="http://lists.racket-lang.org/users/archive/2013-April/057510.html" target="_blank">http://lists.racket-lang.org/users/archive/2013-April/057510.html</a><br>
_________________________<br>
Racket Developers list:<br>
<a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br>
</blockquote></div><br></div>