Shea Leffler

> > > Cool stuff! I am interested in implementing an API for accessing ECS data with minimal restrictions, which would help make scripting language APIs less prone to panics...

> > > > Sounds interesting, but frankly it's completely orthogonal to my use case. :) I need parallel access simultaneously to scripting access, and dynamic typing support at the...

> I think you'll find running things in parallel opportunistically to be problematic due to ordering issues. If positions of bullets are updated in parallel, and scripts are able to...

I think I'm starting to see how this proposed API would be so helpful - a dynamic query could immediately run the query, collect all results, and return them, without...

> Since the API wraps a &mut World, it gets to decide how to make access to the data stored in World safe, and can ignore archetype borrowing. Instead, the...

Thank you for the review! I'm going to try to go through it today. If I understand exactly what you mean by "a more direct AST-based approach", I went with...

> Another relevant factor: how do you envision scripting language constructing/executing queries, if at all? Natively `lift`ing a complex query into a dynamic query is a cool capability, but to...

> That example doesn't seem to contain `lift` at all. I'm guessing it's invoked by `Query.write`/`Query.read`? That doesn't seem to take much advantage of `lift`'s generality. Yes; for reference, under...

@All8Up if I understand correctly, you could benefit from a few mechanisms that I use on the regular with regards to dynamically representing types. `TypeId`s are not the necessary thing...

Ah, I see! I didn't realize you had two different things you needed out of this rough patch of feature-space. Makes sense! :)