bug#45234: Annotation function vs. Affixation function

[Clemens]

> The current implementation assumes that the affixation function
> can be smart enough to recognize that completions were modified
> by a previous call of the annotation function.

The doc says it receives a list of completions so I think currently  you 
would have to look at the code to figure that out. Maybe we could avoid 
that complication? Currently it seems every affixation would need to 
check if it got a list of strings or a list of items as returned by a 
possibly defined annotation function.