[Avocado-devel] Multiplexer design recent discussions summary

[Paolo Bonzini]

On 25/11/2015 16:39, Lukáš Doktor wrote:
> 
>     --mux-mux $path[:true|false] -- to set the node as mux/nomux
>     --mux-inject [$path:]key:value -- to set value (and create the node)
>     --mux-cut $path -- remove any node (opposite of --mux-inject)

--mux-remove?

>     --mux-keep $path -- mux-cut siblings

What's the usecase?

>     --mux-out $path -- remove variants containing this path

--mux-skip?

>     --mux-only $path -- mux-out siblings
> 
> yaml:
> 
>     !mux -- set the node as multiplexed
>     !out : $path -- ignore variants with this $path

!skip?

>     !only : $path -- !out siblings
> 
> The `!out` can be translated to `mux-cut` by using your logic (find the
> precursor which is a direct child of a !mux node and cut it out). So
> `!out`/`!only` can be in fact realized by cutting, should that bring
> some performance improvement.
> 
> I don't see a benefit in implementing `!cut` and `!keep`, because it
> doesn't make sense to me to allow people say "Yes, use this structure,
> but remove some nodes from the result but just for this single variant".

I think !remove makes sense.  I'm not sure what --mux-keep and !keep
would be used for.

Paolo