[Openmcl-devel] Bug bounty

Hans Hübner hans.huebner at gmail.com
Fri Oct 26 09:08:11 PDT 2018


quoting http://clhs.lisp.se/Body/f_rm_rm.htm

*delete* <http://clhs.lisp.se/Body/f_rm_rm.htm#delete>, *delete-if*
<http://clhs.lisp.se/Body/f_rm_rm.htm#delete-if>, and *delete-if-not*
<http://clhs.lisp.se/Body/f_rm_rm.htm#delete-if-not> return a *sequence*
<http://clhs.lisp.se/Body/26_glo_s.htm#sequence> of the same *type*
<http://clhs.lisp.se/Body/26_glo_t.htm#type> as *sequence* that has the
same elements except that those in the subsequence *bounded*
<http://clhs.lisp.se/Body/26_glo_b.htm#bounded> by *start* and *end*
and *satisfying
the test*have been deleted. *Sequence* may be destroyed and used to
construct the result; however, the result might or might not be *identical*
<http://clhs.lisp.se/Body/26_glo_i.htm#identical> to *sequence*

`DELETE` is an optimization to `REMOVE` that may destroy the sequence if it
has to.  Still, you need to save the return value of `DELETE` as there is
no guarantee that the sequence is modified in-place.  I'd assume that
`interval:delete` works the same way.


Am Fr., 26. Okt. 2018 um 18:01 Uhr schrieb Ron Garret <ron at flownet.com>:

> Yeah, pretty sure.  What would I use it for?
> (BTW, I’m pretty sure this is a real bug and not just user error, but if
> I’m wrong about that I’ll still pay the bounty to whoever shows me what I’m
> doing wrong.  Ultimately, all I care about is having interval-tree code
> that’s reliable, efficient, and not too messy.  I don’t really care about
> fixing this bug per se, though I do think that is the easiest path from A
> to B.  But if someone wanted to, say, do a complete re-implentation that
> would probably be OK, but you should check with me first.)
> rg
> On Oct 26, 2018, at 8:50 AM, Hans Hübner <hans.huebner at gmail.com> wrote:
> Ron,
> are you sure you don't need to use the return value of `interval:delete`?
> -Hans
> Am Fr., 26. Okt. 2018 um 17:46 Uhr schrieb Ron Garret <ron at flownet.com>:
>> This is not a CCL bug, but all the cool kids seem to hang out here so...
>> I hereby offer a $500 bug bounty to the first person to publish a fix for
>> this issue:
>> https://github.com/rpav/cl-interval/issues/5
>> This offer expires on Friday, Nov 9, 2018.  That’s not a hard deadline —
>> if you need more time I can accommodate you.  I just don’t want someone
>> trying to claim the bounty a year from now.  Also, I will need your SSN or
>> TIN so I can send you a 1099.
>> If you want to take this on, contact me off-list for some additional info
>> and test cases to help you get started.
>> rg
>> _______________________________________________
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
>> https://lists.clozure.com/mailman/listinfo/openmcl-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clozure.com/pipermail/openmcl-devel/attachments/20181026/6c078862/attachment.htm>

More information about the Openmcl-devel mailing list