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.

Sign up for GitHub

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

Jump to bottom

[SR-218] No way to represent boolean types with NSNumber #42840

Closed
swift-ci opened this issue Dec 13, 2015 · 0 comments
Closed

[SR-218] No way to represent boolean types with NSNumber #42840

swift-ci opened this issue Dec 13, 2015 · 0 comments
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior.

Comments

@swift-ci
Copy link
Collaborator

Previous ID SR-218
Radar None
Original Reporter davbeck (JIRA User)
Type Bug
Status Resolved
Resolution Duplicate
Additional Detail from JIRA
Votes 0
Component/s
Labels Bug
Assignee None
Priority Medium

md5: e6126b314e1e5f45af977d91606ef9b1

duplicates:

  • SR-72 NSNumber is missing much parity

Issue Description:

Or, CFBooleanRef cannot be used as an NSNumber.

CFNumber has no type for bool specifically, instead, it stores them as a char type. Normally, in ObjC Foundation, you would use the constants kCFBooleanTrue and kCFBooleanFalse to represent boolean values explicitly. However, if you try to cast either of those values to NSNumber with SwiftFoundation (i.e. unsafeBitCast(kCFBooleanFalse, NSNumber.self)), it creates an invalid object.
@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
Assignees
No one assigned
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@swift-ci