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-2454] someBool as NSNumber no longer produces kCFBoolean* values #45059

Closed
lilyball mannequin opened this issue Aug 22, 2016 · 0 comments
Closed

[SR-2454] someBool as NSNumber no longer produces kCFBoolean* values #45059

lilyball mannequin opened this issue Aug 22, 2016 · 0 comments
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior.

Comments

@lilyball
Copy link
Mannequin

lilyball mannequin commented Aug 22, 2016

Previous ID SR-2454
Radar None
Original Reporter @lilyball
Type Bug
Status Resolved
Resolution Duplicate
Environment

Apple Swift version 3.0 (swiftlang-800.0.43.6 clang-800.0.38)
Target: x86_64-apple-macosx10.9

Additional Detail from JIRA
Votes 0
Component/s
Labels Bug
Assignee None
Priority Medium

md5: 6893c6d83f3e98f21c714785c9e935a4

duplicates:

  • SR-2381 Swift 3 (Xcode 8 beta 6) archives booleans in XML plist as integers

Issue Description:

Previously, the expression someBoolVar as NSNumber would produce either kCFBooleanTrue or kCFBooleanFalse. As of Xcode 8 beta 6, this is no longer true. Interestingly, true as NSNumber still produces the correct constants.

import Foundation

let b = true
let x = b as NSNumber
print(x === kCFBooleanTrue)

This should print true but it prints false.

@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
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior.
Projects
None yet
Development

No branches or pull requests

0 participants