CGVector should have equivalent constants and functions as other CGGeometry structs

Originator:brandon
Number:rdar://17590909 Date Originated:July 8, 2014
Status:Closed Resolved:December 22, 2014
Product:iOS SDK Product Version:iOS 7, iOS 8 betas
Classification:Enhancement Reproducible:Always
 
Summary:
Trying to use CGVector where semantically appropriate as opposed to just using a CGPoint becomes more difficult because of the lack of constants and functions equivalent to those that are provided for other CGGeometry structs.

Specifically I would expect that there would be a CGVectorZero constant, CGVectorEqualToVector function and CGVectorApplyAffineTransform function.

In addition to these equivalent functions I would expect functions specific to CGVector, like a hypothetical CGVectorNormalize or a number of other functions that perform common operations on vectors such as those seen in https://github.com/samgreen/CGVector-Awesome, to exist and be defined in CGGeometry.h.

Steps to Reproduce:
Attempt to create a zero vector with the constant CGVectorZero.

Expected Results:
I expect that the constant exists and is defined in CGGeometry.h

Actual Results:
The constant is not defined.

Version:
iOS 7, iOS8 betas

Configuration:
All

Comments

Apple Developer Relations

Engineering has determined that there are no plans to address this issue.

We are now closing this bug report.

If this is still a critical issue for you, we recommend you file a new bug report based on the most recent OS, and provide fresh diagnostics.

If you just have questions about the resolution, then please update your bug report with that information so we can respond.

Please be sure to regularly check new Apple releases for any updates that might affect this issue.

By brandon at Dec. 23, 2014, 1:51 a.m. (reply...)

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!