Do you think it would make sense for heron to maintain a QueryPipeline that could be use to do ray-casting and other queries, albeit in a more manual mechanism than we would prefer. #35 has a great idea for what a nice ray casting API would look like, which is great, but I'm looking at adding a QueryPipeline resource that is updated every physics step so I can get started right away and I wondered whether or not I should add it to my library or if you would be open to me adding a PR for it here.
Do you think it would make sense for
heron
to maintain aQueryPipeline
that could be use to do ray-casting and other queries, albeit in a more manual mechanism than we would prefer. #35 has a great idea for what a nice ray casting API would look like, which is great, but I'm looking at adding aQueryPipeline
resource that is updated every physics step so I can get started right away and I wondered whether or not I should add it to my library or if you would be open to me adding a PR for it here.