Christian Clason

This is ready for review @neovim/treesitter @lewis6991

I think we want to park this until after 0.8, when we get a cleaner picture of which utilities are generally useful and which only in the context of nvim-treesitter....

We usually treat optional arguments as an `opts` keyword-value table. This should be the pattern here if we go that route. But, yes, adding options is preferable to adding another...

I meant "design pattern".

This would be necessary in any case, but I don't think we want to merge this before 0.8 (end of month) either way. (Full transparency: which doesn't guarantee that we'll...

Now that Nvim 0.8 is released and the dust has settled somewhat, we should circle back to this (in particular because the next step is to update nvim-treesitter to use...

(patterns/matches are related to predicates and directives, so that's more of question towards generalizing those @lewis6991 )

No, as this will still run _builtin_ plugins. `--clean` was added explicitly because we didn't have a "factory defaults" setting before.

If it's clearer, I can write `no user config, no user plugins`?

If you don't bundle hunspell (which is OK for an optional feature), you need to add it to the build image here: https://github.com/neovim/neovim/blob/22a88c425e2fe99bcb534e43396a0b00044ae67d/.github/workflows/ci.yml#L36