Documentation suggestion: use different types for worker IDs, timestamps, and data

In the current documentation, integers are used for everything: worker identifiers, timestamps, and data. This makes the example code snippets unnecessarily confusing, as one has a harder time figuring out which is which and separating the concepts.

I think the examples would be much easier to understand if they used separate data types for all of these. As IIUC worker identifiers are necessarily integers, this leaves you free to use two other data types for inputs and timestamps. I guess arrays/tuples of integers or floats would make fine inputs, but I am not sure how flexible timely is with respect to timestamps. Is everything that has an ordering fine?

Start by locating the documentation examples that use integers for worker identifiers, timestamps, and data. Check what timestamp types timely accepts and update the examples to use distinct types, while preserving integer worker identifiers. Done means the examples clearly separate these concepts and the documentation explains any timestamp constraints.