[swift-evolution] [Review] SE-0083: Remove bridging conversion behavior from dynamic casts
adrian.zubarev at devandartist.com
Fri May 13 11:11:34 CDT 2016
What is your evaluation of the proposal?
This is a welcome change, which also should open the door to rethink the ObjC `AnyObject` protocol and its confusing .Type `AnyClass`.
Is the problem being addressed significant enough to warrant a change to Swift?
Without a doubt. It feels way better and more elegant to use initializers than worrying about what happens under the hood.
Does this proposal fit well with the feel and direction of Swift?
Yes it does. Swift should be a strong type save language, which will apply to remove strange sideeffects like the unwanted bridging in some specific cases. This also will be the next step after SE-0072.
If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
Not that I can think of.
How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
I carefully read the whole proposal and followed the mailing list. I've been waiting for such a change since I faced the unwanted bridging behaviour in one of my projects amost a year ago. The only workaround for checking a type being a reference-type without bridging was `guard instance.dynamicType is AnyObject.Type else`, which is ugly.
Sent with Airmail
Am 10. Mai 2016 bei 20:53:15, Chris Lattner via swift-evolution (swift-evolution at swift.org) schrieb:
Hello Swift community,
The review of "SE-0083: Remove bridging conversion behavior from dynamic casts" begins now and runs through May 16. The proposal is available here:
Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
or, if you would like to keep your feedback private, directly to the review manager.
What goes into a review?
The goal of the review process is to improve the proposal under review through constructive criticism and contribute to the direction of Swift. When writing your review, here are some questions you might want to answer in your review:
* What is your evaluation of the proposal?
* Is the problem being addressed significant enough to warrant a change to Swift?
* Does this proposal fit well with the feel and direction of Swift?
* If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
* How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
More information about the Swift evolution process is available at
swift-evolution mailing list
swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution