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

[SR-1851] Create apinotes for the Security framework #44460

Closed
swift-ci opened this issue Jun 21, 2016 · 4 comments
Closed

[SR-1851] Create apinotes for the Security framework #44460

swift-ci opened this issue Jun 21, 2016 · 4 comments

Comments

@swift-ci
Copy link
Collaborator

Previous ID SR-1851
Radar None
Original Reporter mgriepentrog (JIRA User)
Type Improvement
Status Resolved
Resolution Invalid
Additional Detail from JIRA
Votes 0
Component/s
Labels Improvement, SDKOverlay
Assignee @milseman
Priority Medium

md5: 9e6097b185ad762635a1f064d583f9a7

Issue Description:

It'd be awesome if we could have an apinotes file for the Security framework, similar to what was done for CoreGraphics. I looked into this a bit myself, and I'd be willing to take this on, but I'm not sure if it's possible to annotate functions that take a pointer and use that pointer to store its result. Example:

func SecCertificateCopyCommonName(_ certificate: SecCertificate, _ commonName: UnsafeMutablePointer<CFString?>) -> OSStatus
@belkadan
Copy link
Contributor

Sorry, but this is not the place to file bugs about Apple frameworks other than those that have APIs that have gone through the Swift Evolution Process. Please file a report at bugreport.apple.com.

@milseman
Copy link
Mannequin

milseman mannequin commented Jun 21, 2016

And please include the radar number here so that we can help bring it along

@swift-ci
Copy link
Collaborator Author

Comment by Mike Griepentrog (JIRA)

Sorry, I spoke to @milseman last week at WWDC about the possibility of doing this, and wanted a way to follow up on it. Aside from filing a radar, what's the best way to move forward? SE-0088 mimics what I want to propose for the Security framework, but the Security framework is not a part of the standard library, and it's been stated that "swift-evolution isn’t the right place to propose changes for Foundation or other APIs outside of the standard library." [1]

[1] https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160530/019902.html

@belkadan
Copy link
Contributor

I'm…not sure there's anything really to say here. API design of Apple frameworks isn't something for which Apple has traditionally looked to outside people for help. Any Swift-side redesign of the Security framework would be run by the Security team, and it would be up to them how much to engage the Swift community. (As an example, SE-0044 went through the evolution process, but the actual changes to Core Graphics did not.)

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants