Re: Smarter matcher-list: skip previous sets

[Daniel Hahler <genml+zsh-workers@xxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19.05.2015 02:44, Bart Schaefer wrote:
> On May 19, 12:11am, Daniel Hahler wrote:
> }
> } I've noticed that my matcher-list setup causes a (possibly expensive)
> } completion function to be called multiple times, although the input was
> } not changed by the matcher-list substitution.
> }
> } I think it would be smart if these calls would be skipped in case the
> } input has not changed (because it was all lower-case in the beginning).
>
> Unfortunately the matcher-list is handled as a loop in the shell code in
> _main_complete, which has no way to tell whether the "input" is or is not
> "changed" by any particular matcher.  You're assuming an implementation
> of matchers that doesn't (ahem) match what actually happens internally.
>
> Matchers don't "change" the input in any way; they alter the comparison
> of the input to the set of possible results, and each such comparison is
> independent of those that preceded it.  The *output* may be changed based
> on which elements of the result set are selected.

But is it necessary then to call the completion function multiple times?
Couldn't the matchers just loop over the result that has been collected
once?

If I understand it correctly, the possible results would be the same
every time?  (at least that's the case for the expensive completion
function, where I've noticed it).

Where is the $_matcher used?
Is it in Completion/Base/Core/_description, in the opts to compadd?

What would be a possible solution to improve handling with many
completers/matchers?


Regards,
Daniel.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iD8DBQFVWvlGfAK/hT/mPgARAigUAKCiubdTM7JYYRlA1d2muHFm4O/v0ACg/IvO
xHLF7p+ny8de/8RwASKHMjc=
=AsuP
-----END PGP SIGNATURE-----