On Thu, Jul 11, 2019 at 06:22:25PM +0200, Julien Rouhaud wrote:
> I think t hat it makes the code quite cleaner to have the selection
> outside ConsumeIdleSlot.
Actually, you have an issue with ConsumeIdleSlot() if there is only
one parallel slot, no? In this case the current patch returns
immediately the slot available without waiting. I think that we
should wait until the slot becomes free in that case as well, and
switch isFree to false. If you want to keep things splitted, that's
fine by me, I would still use "Get" within the name for the routine,
and rename the other to get_idle_slot_internal() or
get_idle_slot_guts() to point out that it has an internal role.
> You're talking about getQuerySuccess right? That was actually the
> original comment of a function I renamed. +1 to improve it, but this
> function is in common.c and doesn't deal with parallel slot at all, so
> I'll just drop the slang parts.
If we can design a clean interface with better comments, we can use
this occasion to browse the whole thing and make it better.
--
Michael