-
Notifications
You must be signed in to change notification settings - Fork 192
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
extensions: make naming and layout consistent across all extensions #494
Conversation
cda2c50
to
bb29817
Compare
I guess we want to get this in after #495? |
The two PRs are independent AFAIK. |
This PR also converts some of the |
Ok. Makes sense. |
cb41ef9
to
6eef4c7
Compare
6eef4c7
to
10e8bab
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not seeing any red flags with this PR, looks good overall. Thanks for the hard work!
23417a2
to
1f9af3b
Compare
You're welcome. Just pushed some commit log rewording. |
There are two "extensions" I left untouched:
|
21c5ddc
to
e945b88
Compare
breaking change: - some extensions were exposing `instance()` instead of `device()` includes: - renaming function pointer member to `fns` - moving `name()`, `fp(`), `device()`/`instance()` functions at end of file - adding missing `device()`/`instance()` functions see ash-rs#493
e945b88
to
5bf1a06
Compare
5bf1a06
to
1cd41a7
Compare
Changelog.md
Outdated
### Changed | ||
|
||
- Device extension `ext::ExtendedDynamicState` now exposes `fn device()` instead of `fn instance()` (#494) | ||
- Device extension `khr::PushDescriptor` now exposes `fn device()` instead of `fn instance()` (#494) | ||
- Device extension `khr::PipelineExecutableProperties` now exposes `fn device()` instead of `fn instance()` (#499) | ||
- Changed `khr::PipelineExecutableProperties::new()` to take `instance` and `device` as arguments (#499) | ||
- Device extension `khr::TimelineSemaphore` now exposes `fn device()` instead of `fn instance()` (#499) | ||
- Changed `khr::TimelineSemaphore::new()` to take `instance` and `device` as arguments (#499) | ||
|
||
### Removed | ||
|
||
- Removed `device` argument from `ext::DebugMarkers::debug_marker_set_object_name` function (#494) | ||
- Removed `From<vk::Result>` trait for `VkResult` (#495) | ||
- Removed `instance` argument from `ext::DebugUtils::submit_debug_utils_message` function (#499) | ||
- Removed `device` argument from `khr::PipelineExecutableProperties` functions (#499) | ||
- Removed `device` argument from `khr::TimelineSemaphore` functions (#499) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, also for taking care of #499. Just not sure if we should mention some single PRs this often in the changelog.
For example, the ### Removed
section is afaik for removed API - changing the arguments to remove ie. device
that's already available in the struct is already documented under ### Changed
, no need to repeat that again.
Furthermore, we can probably make lists, ie turn this:
- Device extension `ext::ExtendedDynamicState` now exposes `fn device()` instead of `fn instance()` (#494)
- Device extension `khr::PushDescriptor` now exposes `fn device()` instead of `fn instance()` (#494)
- Device extension `khr::PipelineExecutableProperties` now exposes `fn device()` instead of `fn instance()` (#499)
into:
- Device extensions `ext::ExtendedDynamicState`, `khr::PushDescriptor` and `khr::PipelineExecutableProperties` now expose `fn device()` instead of `fn instance()` (#494, #499)
I think that's much more more concise (more readable).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Ralith What are your thoughts on this, and this PR in general? Seems to be pretty much ready to go in besides some changelog bikeshedding, unless you have some burning comments?
Would like to get this in and do a release soon, it has been way too long.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your proposed tweaks to the changelog SGTM, and overall this looks like great cleanup, though I haven't reviewed every single change in detail.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes are pretty boring. It's mostly code gardening.
Could help if we want to generate that code in the future though.
PS: Redacting the Changelog is actually harder than it was doing the code changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@filnet Yes, curating the changelog (usually when preparing for a release) is pretty tough. We usually end up going for just the commit titles since the last release, but that's usually not fully representative nor are all the titles good enough for direct use :)
Changelog.md
Outdated
### Changed | ||
|
||
- Device extension `ext::ExtendedDynamicState` now exposes `fn device()` instead of `fn instance()` (#494) | ||
- Device extension `khr::PushDescriptor` now exposes `fn device()` instead of `fn instance()` (#494) | ||
- Device extension `khr::PipelineExecutableProperties` now exposes `fn device()` instead of `fn instance()` (#499) | ||
- Changed `khr::PipelineExecutableProperties::new()` to take `instance` and `device` as arguments (#499) | ||
- Device extension `khr::TimelineSemaphore` now exposes `fn device()` instead of `fn instance()` (#499) | ||
- Changed `khr::TimelineSemaphore::new()` to take `instance` and `device` as arguments (#499) | ||
|
||
### Removed | ||
|
||
- Removed `device` argument from `ext::DebugMarkers::debug_marker_set_object_name` function (#494) | ||
- Removed `From<vk::Result>` trait for `VkResult` (#495) | ||
- Removed `instance` argument from `ext::DebugUtils::submit_debug_utils_message` function (#499) | ||
- Removed `device` argument from `khr::PipelineExecutableProperties` functions (#499) | ||
- Removed `device` argument from `khr::TimelineSemaphore` functions (#499) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your proposed tweaks to the changelog SGTM, and overall this looks like great cleanup, though I haven't reviewed every single change in detail.
1cd41a7
to
d4d8a27
Compare
46b8af5
to
5de9ed4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving wrt. the issues I've previously specifically highlighted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changelog seems fine besides this - will re-re-re-review the rest of the code later on :)
5de9ed4
to
78197b7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks good now. Thanks for your perseverance in dealing with all the review comments and repeated large changes!
breaking change:
includes:
using result() instead of into()