Jad Abou-Chakra

I can give it a shot, but maybe you can point me in the right direction. What is the mechanism used here for creating the python bindings. It doesn't seem...

For example: to add ```dds_get_subscription_matched_status```, would I add it after [@c_call("dds_reader_wait_for_historical_data")](https://github.com/eclipse-cyclonedds/cyclonedds-python/blob/2b5231f620b9643b6651dc9647eb5dfbbd4fec0b/cyclonedds/sub.py#L386). It would be ```python @c_call("dds_get_subscription_matched_status") def _get_subscription_matched_status(self, reader: dds_c_t.entity, status: dds_c_t.status) -> dds_c_t.returnv: pass ``` I don't think dds_c_t.status...

It actually looks like someone has done this already: https://github.com/eclipse-cyclonedds/cyclonedds-python/pull/43/commits/da14e5b17004e1924e22b727ca916439a595dff6

Do you accept pull requests? If so, I'm happy to add it

It looks like callbacks were added into the opengl renderer that allow this to happen :).

Thank you for considering the request. I think not including it to avoid feature creep is fair enough. Writing the function is simple enough that it doesn't need to be...

Adding this enhancement may also allow ```warp.sim.State``` and ```warp.sim.Control``` to be marked as ```wp.struct``` and thus passed directly into kernels?

The same is true of range(). Would be good if ```for i in range(idx)``` worked if idx is uint32

It doesn't work on linux either. I get: ``` Error: × failed to extract metadata for 'python_bindings' ├─▶ failed to communicate with the build backend (pixi-build-cmake) ├─▶ ErrorObject { code:...