Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VK_NV_device_diagnostic_checkpoints: Enable passing pNext-initialized structs to get_queue_checkpoint_data #588

Merged
merged 1 commit into from
Mar 22, 2022

Conversation

MarijnS95
Copy link
Collaborator

To match all other functions which accept an array of to-be-initialized structs with a pNext pointer that is possibly initialized by the caller.

@MarijnS95 MarijnS95 force-pushed the device-diagnostic-checkpoints branch from b04d8b5 to a05fb7b Compare February 23, 2022 13:58
@MarijnS95 MarijnS95 changed the title device_diagnostic_checkpoints: Allow passing pNext-initialized structs VK_NV_device_diagnostic_checkpoints: Allow passing pNext-initialized structs to get_queue_checkpoint_data Feb 23, 2022
@MarijnS95 MarijnS95 changed the title VK_NV_device_diagnostic_checkpoints: Allow passing pNext-initialized structs to get_queue_checkpoint_data VK_NV_device_diagnostic_checkpoints: Enable passing pNext-initialized structs to get_queue_checkpoint_data Mar 17, 2022
@MarijnS95 MarijnS95 force-pushed the device-diagnostic-checkpoints branch from a05fb7b to 51cba45 Compare March 17, 2022 10:14
…ucts to `get_queue_checkpoint_data`

To match all other functions which accept an array of to-be-initialized
structs with a `pNext` pointer that is possibly initialized by the
caller.
@MarijnS95 MarijnS95 force-pushed the device-diagnostic-checkpoints branch from 51cba45 to d7ad60c Compare March 22, 2022 22:51
@MarijnS95 MarijnS95 merged commit 7779771 into master Mar 22, 2022
@MarijnS95 MarijnS95 deleted the device-diagnostic-checkpoints branch March 22, 2022 23:07
MarijnS95 added a commit that referenced this pull request Dec 2, 2024
…`pNext`

We've often discussed `pNext` chains in output arrays (i.e. #465, #588,
 #744), and I always wondered why `read_into_defaulted_vector()` still
existed: turns out this helper function was only hiding a few more
remaining cases where the caller was previously _not_ able to manually
extend the `pNext` chain to request arbitrary more structures to be
filled with information.

Replace these remaining cases with a separate `_len()` getter, and have
the main function take a caller-allocated `&mut [T]` slice where they
can initialize the target struct including `pNext` pointer chains.
MarijnS95 added a commit that referenced this pull request Dec 3, 2024
…`pNext`

We've often discussed `pNext` chains in output arrays (i.e. #465, #588,
 #744), and I always wondered why `read_into_defaulted_vector()` still
existed: turns out this helper function was only hiding a few more
remaining cases where the caller was previously _not_ able to manually
extend the `pNext` chain to request arbitrary more structures to be
filled with information.

Replace these remaining cases with a separate `_len()` getter, and have
the main function take a caller-allocated `&mut [T]` slice where they
can initialize the target struct including `pNext` pointer chains.
MarijnS95 added a commit that referenced this pull request Dec 4, 2024
…`pNext`

We've often discussed `pNext` chains in output arrays (i.e. #465, #588,
 #744), and I always wondered why `read_into_defaulted_vector()` still
existed: turns out this helper function was only hiding a few more
remaining cases where the caller was previously _not_ able to manually
extend the `pNext` chain to request arbitrary more structures to be
filled with information.

Replace these remaining cases with a separate `_len()` getter, and have
the main function take a caller-allocated `&mut [T]` slice where they
can initialize the target struct including `pNext` pointer chains.
MarijnS95 added a commit that referenced this pull request Dec 4, 2024
…`pNext` (#966)

We've often discussed `pNext` chains in output arrays (i.e. #465, #588,
 #744), and I always wondered why `read_into_defaulted_vector()` still
existed: turns out this helper function was only hiding a few more
remaining cases where the caller was previously _not_ able to manually
extend the `pNext` chain to request arbitrary more structures to be
filled with information.

Replace these remaining cases with a separate `_len()` getter, and have
the main function take a caller-allocated `&mut [T]` slice where they
can initialize the target struct including `pNext` pointer chains.
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.

2 participants