You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of Unified Runtime we need to provide a migration guide documenting the mapping from the PI plugin API to UR. This should consist of a set of mappings between the various entry points, types enumerations etc. and any divergences in semantics.
i.e. something like
Functions
PI
UR
Differences
piDeviceGetInfo
urDeviceGetInfo
None
...
...
...
...
...
...
Types
PI
UR
Differences
pi_context
ur_context_handle_t
None
...
...
...
...
...
...
Enumerations
PI
UR
Differences
pi_device_info
ur_device_info
(list of removed queries)
...
...
...
...
...
...
The initial proposal is to do this in markdown and have a living document in this repo that can be update as spec changes are made.
The text was updated successfully, but these errors were encountered:
The handwritten portions of the spec are reStructureText. I feel like this should be part of the spec document rather than separate. That implies writing the migration guide in reStructuredText not Markdown.
Sure reStructureText works just as well for me. @kbenzie Are you happy with the laying this out in tables like above? rst has better support for tables so it's probably a better choice anyway if we are going to go with that.
As part of Unified Runtime we need to provide a migration guide documenting the mapping from the PI plugin API to UR. This should consist of a set of mappings between the various entry points, types enumerations etc. and any divergences in semantics.
i.e. something like
Functions
Types
Enumerations
The initial proposal is to do this in markdown and have a living document in this repo that can be update as spec changes are made.
The text was updated successfully, but these errors were encountered: