I think you said yourself that this might not be common enough to bother addressing? That doesn’t sound like it calls for shifting the burden to developers in a non-extensible and non-uniform way. Keeping in line with existing patterns is better for people trying to use it as well. If you saw the special case in the wild you would have to look up the spec to work out what it means — it deviates from the way name variables work, and it does so it in a subtly different way from how the original “editortranslator” collapse works with terms. With the “if” approach, there is no new syntax, no new behaviour, and you don’t need to look up anything. So “shifting the burden” as I described it is inaccurate; you would just be creating burdens all round.