Jeremy Leibs

Note: I don't believe this entire issue need to be resolved to decide on the name / direction for the temporal batch APIs for 0.18. However, if we introduce `send_`...

I realized we didn't specify what to do with tombstones as part of https://www.notion.so/rerunio/Repeated-Time-Values-10bb24554b1980d8a0cdcca3d8903502 I agree generally hiding them from the view makes sense for now.

Reminder to self: make sure docs cover when you need to use unique app-ids (such as when blueprint is a function of data)

Exactly. We were getting a link error. Thanks for the pointers. I'll check the versions and see if we're using rustix tomorrow -- we might be one version behind.

Possible small improvements: - Better text when nothing is found? - When there are **multiple** entity expressions, warn if any single entity expression doesn't contribute content.

This proposal makes sense to me. Something else worth considering: we eventually want to provide an API in which users can explicitly control the timepoint associated with their data instead...

- I believe https://github.com/rerun-io/rerun/issues/6807 also requires bringing in a dependency on `arrow`

You can also do: ``` rr.log_components("points", [rr.components.ColorBatch([0xFF0000FF])], num_instances=2) ```

This is an interesting one. Needs some kind of archetype-aware handling in `rr.log`, or an optional interface we check on the `AsComponents`?

Conclusion from talking with @nikolausWest -- for now we will continue to make this explicit in the APIs. For 0.9 let's go through and make sure every ViewCoordinate and AnnotationContext...