<div>Sorry if this double posts.</div><p>I just wanna say, as a new member, I'm impressed by the speed, volume, and quality of responses in this community. Not being simply told to RTFM or such is a really great change from many other places.</p>
<p> </p><p class="im">
</p><div>> Or use structure properties to turn them into sequences (and then use for and </div><div>> friends).</div><p> </p><p>That would work for the TO-LIST abstraction or for using a sequence as an intermediate representation for collection types. But, what about something like the Speakable behaviorial type? </p>
<p class="im">
</p><p> </p><p>> I imagine that one could use impersonators for vectors and _mutable_ lists.</p><p> </p><p>Racket's a pretty big language. I think everytime I try and do something, I end up in a new unexplored corner of the language. I'll check impersonators out, though according to Sam's comment they won't necessarily work.</p>
<p class="im">
</p><p> </p><p>> You could do that, or you could handle them specially in your generic</p><p>> function.</p><p> </p><p>That's probably the most straight forward way, but it means dealing with built-in types upfront rather than allowing for later extensibility (unless I missed something).</p>
<p style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
</p><p> </p><p> </p><p style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
</p><div> </div>