[racket-dev] indentation: the rb tree didn't help, but a hack to stick-to-next-sexp might

If you're really worried about the allocation, you can work at the
snip level and pass in a buffer to be filled in with characters, you
know. :)

On Mon, Nov 26, 2012 at 2:44 PM, Danny Yoo <dyoo at hashcollision.org> wrote:
>
>> and call it a bunch (inside an 'or', one branch for each of those
>> strings that are currently in the second argument to member; or well,
>> even use a for/or, I guess). Or, if you wanted, you could change your
>> existing code to push the 'or' inside the 'and' and then drop the
>> promise.
>
>
>
> Ok, I'll rewrite the code without the promise, and push to master.