Return missing component types in QueryDoesNotMatch errors

[SignalWalker]

What problem does this solve or what need does it fill?

When handling QueryEntityError::QueryDoesNotMatch from Querys over multiple component types, it'd be useful for debugging to be able to check which components were missing.

What solution would you like?

The first that comes to mind is to just put a Vec of component names in the error type, but it doesn't have to be that -- I just want to be able to find out without having to manually check each component. Maybe a Query::get_missing function?

What alternative(s) have you considered?

• Instead of Query<(X, Y)>, use Query<(Option<X>, Option<Y>)> -- this isn't very ergonomic, though, especially when the component isn't actually intended to be optional.

Related PRs

• Document query errors #8692

[Selene-Amanita]

Additionally, those "Query[Something]Error" types could return more informations on other cases:

• QueryComponentError variants could contain the Entity that was requested, like QueryEntityError variants do
• QueryComponentError variants could contain a representation of the Component that was requested
• QueryComponentError variants and QueryEntityError variants could contain a &str representation of the query, like QuerySingleError variants do, using std::any::type_name()
• I realize now that I didn't document that QueryEntityError contain the Entity and QuerySingleErrorcontain a &str of the query in Document query errors #8692.

Those are less useful (and technically an other issue) because technically you should know those informations (/have them at hand) when you write the code and call the function that triggers them, contrary to knowing what went wrong with QueryEntityError::QueryDoesNotMatch which is what that PR is about, but having those additional informations inside the "Query[Something]Error" types could allow to have a function that handles error from different parts of the code.

Note: the &str variant of the query could be replaced by a generic type of the error, to avoid processing it and storing it if not needed, but would probably increase the compilation time/size of the binary for no reason.