> * What is your evaluation of the proposal?
+1
> * Is the problem being addressed significant enough to warrant a change
> to Swift?
Yes, the current-state leaves one unable to do certain things in pure Swift
(e.g. tagged pointers) that are clearly useful on occasion.
> * Does this proposal fit well with the feel and direction of Swift?
I do think from the alternatives mentioned that the suggested approach is the
cleanest. This sort of programming clearly belongs in the “unsafe” corner, but
that doesn’t mean one shouldn’t be able to express these sorts of things in
Swift.
> * If you have you used other languages or libraries with a similar
> feature, how do you feel that this proposal compares to those?
I have not used any aspiring system programming languages that didn’t allow
manipulating pointers as integer values.
> * How much effort did you put into your review? A glance, a quick
> reading, or an in-depth study?
A quick read of the proposal.
Daniel.
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
