You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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]
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.)
Additional Detail from JIRA
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:
The text was updated successfully, but these errors were encountered: