Simon,
> <sigh> This post isn't really very helpful. You aren't providing the
> second part of the discussion, nor even requesting that this issue be
> fixed. I can see such comments being taken up by people with a clear
> interest in dissing HS.
OK, I'm requesting that the issue be fixed. I'm not sure if it needs to
be fixed before Alpha3. I got the impression from you that others did
not think this issue really needed fixing.
> Heikki and I had mentioned that solving this need not be part of the
> initial patch, since it wouldn't effect all users. I specifically
> removed my solution in July/Aug, to allow the patch to be slimmed down.
I guess I don't understand which users wouldn't be affected. It seems
like the only users who would avoid this is ones who don't do deletes or
index-affecting updates.
>>From my side, the purpose of discussing this was to highlight something
> which is not technically a bug, yet clearly still needs work before
> close. And it also needs to be on the table, to allow further discussion
> and generate the impetus to allow work on it in this release.
Yes. I'm realizing that because of the highly techincal nature of the
discussion and the language used few people other than you and Heikki
are aware of the major issues which still need work. It would be
helpful if someone could post a summary of outstanding issues which
didn't require prior extensive experience with the HS code to
understand; possibly you could then get people trying to tackle just
those individual issues.
--Josh BErkus
