Better understanding or maybe Documentation? about hecs

[Ralith]

Have you read the API docs for those types?

[genusistimelord]

yes I have and they did not make sense to me tbh.

https://docs.rs/hecs/latest/hecs/struct.With.html if this is what your talking about.
as when I look at this it doesn't really tell me what Q and R are for. so its a trail and error game to figure it out.

Also with Satisfies I am guessing it just a boolean to determine if something Exists. Can it be mixed with With and Without?

[Ralith]

it doesn't really tell me what Q and R are for

The example illustrates a query where Q is evaluated, but restricted to entities that match R. It also cites a similar illustration in QueryBorrow::with.

Can it be mixed with With and Without?

If a type variable is introduced like Q: Query, that means it can accept any type that implements Query. All of With, Without, and Satisfies implement Query.

[genusistimelord]

sorry I just did not understand the example itself. So i had to make a little test that printed off what it did find in each query. Just saying it would be nice to just have it Say on there either in the description or a comment above the example explaining what it is doing. Also adding the assert kind of works but maybe adding another assert that fails due to lets say c not existing in the queue would help make it more obvious. It is just a different way of thinking on my part sorry.

I can Expand the docs if you would like and add more examples for things. just I gotta figure out how to use each part. could you show me an example of how to use Satisfies with With and Without on how it might be used to determine if something should be shown or not maybe.

[Ralith]

Thanks for the feedback; I agree that referring to the type parameters by name improves clarity here.

I don't think we specifically need examples of combining these in particular. You can always use any type that implements Query in any type variable that requires Query, just like with any other Rust generics. For example, With<Without<Satisfies<Q>, R>, S> gives you a query that yields a bool indicating whether an entity matches Q for each entity that matches S and does not match R.

[genusistimelord]

Ahh nice. Yeah, the more clarity there is the better and easier it becomes to learn.