+1 converting to a string is definitely lossy for most cases. On Wed, May 18, 2016 at 12:09 AM, Jacob Bandes-Storch via swift-evolution < [email protected]> wrote:
> * What is your evaluation of the proposal? >> > > +1, because: > - I believe the default/generic "printing" initializer is not commonly > used (at least, not on purpose). > - The new argument label clearly indicates what the initializer does. > > I would also submit for consideration "*init(describing:)*", to match the > CustomStringConvertible ".description" property which it invokes. > > >> * Is the problem being addressed significant enough to warrant a >> change to Swift? >> > > Yes: accidental use of the initializer can be harmful, and is currently > very easy. > > >> * Does this proposal fit well with the feel and direction of >> Swift? >> > > Yes, it fits well with the API guidelines. > > >> * If you have used other languages or libraries with a similar >> feature, how do you feel that this proposal compares to those? >> > N/A > > >> * How much effort did you put into your review? A glance, a quick >> reading, or an in-depth study? >> > > A quick reading. > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution > >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
