Update cuda-core release notes: Add missing milestone 19 PRs #881
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the cuda-core 0.X.Y release notes to include two important PRs that were merged as part of milestone 19 ("cuda.core beta 7") but were missing from the release notes.
Changes Made
Added release note entries for:
StridedMemoryView performance improvement (PR Improve #449: Improve StridedMemoryView creation time #838): Optimized the creation time performance by using Python/C API for shape and strides tuple creation, reducing creation time from 1.23 μs to 1.02 μs (~17% improvement).
GraphBuilder.add_child bug fix (PR Fix an apparent mistake in GraphBuilder.add_child #879): Fixed a bug where dependencies extracted from capturing stream were passed inconsistently with the num_dependencies parameter obtained from the cuStreamGetCaptureInfo call.
Background
While reviewing the merged PRs from milestone 19, I identified that several important cuda-core improvements had been merged but were not reflected in the release notes. This ensures that users are properly informed about:
The release notes now accurately reflect all functional changes to cuda-core that were delivered in milestone 19.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.