Nope, not important enough at all. The current implementation identifies all byte sequences identically to mine.
On Mon, Jun 13, 2016 at 1:26 PM, Richard Hipp <d...@sqlite.org> wrote: > On 6/13/16, Scott Robison <sc...@casaderobison.com> wrote: > > I like [my lookslike.c function] more than the existing... > > Apparently other people do too. However, if I hold up the release of > 1.35 until your new function gets in, that will delay the release > until August at the earliest, due to other scheduling issues. > > So the question becomes: Is your enhancement important enough to > delay the release by two months? Or is it better to get 1.35 out > Tuesday morning and deal with your enhancement for 1.36? > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > fossil-dev mailing list > fossil-dev@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev > -- Scott Robison
_______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
