Skip to content

Conversation

PiotrSikora
Copy link
Member

While there, add and consistently use UNKNOWN_RESOURCE_ID error
for when resources are accessed using an unknown ID.

While there, add and consistently use `UNKNOWN_RESOURCE_ID` error
for when resources are accessed using an unknown ID.

Signed-off-by: Piotr Sikora <[email protected]>
Comment on lines 235 to 243
* returns:
- `i32 (`[`proxy_status_t`]`) status`

> **Warning**
> This function has been deprecated in favor of explicit context IDs.
Changes the effective context to `context_id`.

This can be used to change active context, e.g. during
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps it should be completely removed?


| Identifier | Name | Values | Deprecated |
|:----------:|:--------------------------------|:---------------------------------------------------------------------------------------------------|:----------:|
| 0x1001 | `HOST_TRACKS_ACTIVE_CONTEXT_ID` | When `1`, `context_id` can be set to `0`, which then indicates host-tracked active context ID. | Yes |
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I originally envisioned this as a helpful step to ease the migration (i.e. SDKs could simply pass 0 as context_id and rely on hosts doing the tracking), but I'm not sure if that's worth it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant