[swift-evolution] [Review] SE-0166: Swift Archival & Serialization

[Zach Waldowski]

I want to disagree with this is strongly as possible lest it influence
the proposal in any way whatsoever. Just because you can solve something
through reflection doesn't mean you should.

  Zachary Waldowski
  zach at waldowski.me

On Wed, Apr 12, 2017, at 03:22 PM, Brad Hilton via swift-evolution
wrote:
> -1. I support the motivation, but I think this proposal and SE-0167 are
> too premature.
> 
> Don’t get me wrong, I think that Swift leaves much to be desired as far
> as serialization/deserialization goes. However I think that these
> proposals are putting the cart before the horse. I think we first need to
> add genuine reflection APIs before adding encoding/decoding capabilities
> to the stdlib. Reflection will substantially simply most
> serialization/deserialization task. These APIs borrow too much Cocoa’s
> native archiving capabilities for my taste and I’d rather not introduce
> something that may be considered legacy in the future.
> 
> 
> > Hello Swift community,
> > 
> > 
> > The review of SE-0166 "Swift Archival&Serialization" begins now and runs through April 12, 2017. The proposal is available here:
> > 
> > > https://github.com/apple/swift-evolution/blob/master/proposals/0166-swift-archival-serialization.md
> > Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> > 
> > > https://lists.swift.org/mailman/listinfo/swift-evolution
> > or, if you would like to keep your feedback private, directly to the review manager. When replying, please try to keep the proposal link at the top of the message:
> > 
> > > 
> > > Proposal link:
> > > 
> > > > https://github.com/apple/swift-evolution/blob/master/proposals/0166-swift-archival-serialization.md
> > > 
> > > Reply text
> > > > Other replies
> > > 
> > What goes into a review?
> > 
> > The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine 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
> > 
> > > https://github.com/apple/swift-evolution/blob/master/process.md
> > Thank you,
> > 
> > 
> > -Doug
> > 
> > 
> > Review Manager
> > 
> > 
> > 
> > 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution