Xcode 7.2b3 (7C62): [Swift] ManagedProtoBuffer's withUnsafeMutablePointer* function arguments should be marked @noescape
| Originator: | janoschhildebrand | ||
| Number: | rdar://23519592 | Date Originated: | 12-Nov-2015 |
| Status: | Open | Resolved: | |
| Product: | Developer Tools | Product Version: | Xcode 7.2b3 |
| Classification: | Enhancement | Reproducible: | Always |
Summary: The three functions withUnsafeMutablePointerToValue<R>(...) withUnsafeMutablePointerToElements<R>(...) withUnsafeMutablePointers<R>(...) of ManagedProtoBuffer all take closures that are immediately executed and not stored. Therefore the closure argument should be marked @noescape. Steps to Reproduce: 1. Open the documentation for ManagedProtoBuffer 2. Check whether the `body` arguments for withUnsafeMutablePointerToValue, withUnsafeMutablePointerToElements and withUnsafeMutablePointers are marked @noescape Expected Results: @noescape Actual Results: No @noescape Version: Xcode 7.2b3 (7C62) Swift version 2.1.1 (swiftlang-700.1.101.13 clang-700.1.81) OS X 10.11.1 (15B42)
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!