[stdlib]Catch the reasonable mistake 'UnsafeRawMutableBufferPointer' #69881
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@swift-ci Please smoke test |
|
@devKobe24 thanks! This illustrates the behaviour you intend, but would not change the toolchain. The typealias would need to be in the standard library code, e.g. alongside the definition of |
I restored the code to its original state in 'test/stdlib/UnsafePointerDiagnostics.swift
|
@swift-ci Please smoke test |
|
Hello, Thank you so much for enlightening me on the crucial aspects. It's my first contribution, and I'm quite nervous and excited, haha. It's such a fun and thrilling adventure. Sincerely from Korea, Kobe. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
[stdlib]Catch the reasonable mistake 'UnsafeRawMutableBufferPointer'
Issue: [SR-6360]
Tag: #48910
We could make things easier on people by adding an unavailable typealias with a renamed field.
Resolve: #48910, fix: #69881
cc: @glessard