<div style="white-space:pre-wrap">Does "lossless" preclude floating-point numbers from being printed in decimal unless they are exactly representable?</div><br><div class="gmail_quote"><div dir="ltr">On Fri, May 27, 2016 at 9:04 PM Austin Zheng via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Thanks, I like "Lossless" too. Further suggestions on naming would be appreciated from anyone.<div><br></div><div></div></div><div style="word-wrap:break-word"><div>Austin</div></div><div style="word-wrap:break-word"><div><br><div><br><div><blockquote type="cite"><div>On May 27, 2016, at 9:03 PM, Xiaodi Wu <<a href="mailto:xiaodi.wu@gmail.com" target="_blank">xiaodi.wu@gmail.com</a>> wrote:</div><br><div>This looks good. I like your use of the term "lossless"; perhaps we can use it consistently, i.e. LosslessStringConvertible. The implication by comparison would be that CustomStringConvertible makes no guarantee of losslessness.<br><div class="gmail_quote"><div dir="ltr">On Fri, May 27, 2016 at 23:52 Austin Zheng via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello swift-evolution,<div><br></div><div>I've put together a preliminary v2 of the proposal, taking into account feedback expressed on this thread. I would appreciate any comments, suggestions, or criticisms.</div><div><br></div><div><a href="https://github.com/austinzheng/swift-evolution/blob/az-edit-89/proposals/0089-rename-string-reflection-init.md" target="_blank">https://github.com/austinzheng/swift-evolution/blob/az-edit-89/proposals/0089-rename-string-reflection-init.md</a><br></div><div><br></div><div>If any objections can be worked out quickly, I hope to resubmit this proposal for review early next week.</div><div><br></div><div>Best,</div><div>Austin</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 27, 2016 at 7:50 PM, Patrick Smith via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is there any possibility we can break from this? Especially as:<br>
<br>
1. ValuePreservingStringConvertible expects its description to be value preserving, but current Cocoa implementations are not.<br>
2. ‘Description’ doesn’t really convey the meaning of ‘value preserving’ in my mind, but is a valuable name for many other use cases.<br>
3. Swift 3 has a wide range of breaking changes for the better.<br>
4. With the presence of ValuePreservingStringConvertible, CustomStringConvertible doesn’t seem to provide much value over CustomDebugStringConvertible?<br>
<br>
For string interpolation, I imagine the standard library could fall back to a ‘description’ method for NSObject subclasses.<br>
<br>
Thanks,<br>
<br>
Patrick<br>
<div><div><br>
> On 28 May 2016, at 7:49 AM, Dave Abrahams via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
><br>
> on Thu May 26 2016, Patrick Smith <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
><br>
>>> On 27 May 2016, at 2:40 PM, Austin Zheng via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
>>><br>
>>> Any of the NSObject subclass candidates may require their<br>
>>> `description`s to be altered to meet the semantics, which may or may<br>
>>> not be an acceptable breaking change.<br>
>><br>
>> Do you think it might be worth changing `description` to be named<br>
>> something else? Something more clear, less likely to conflict with<br>
>> ‘real’ properties — ‘description’ doesn’t seem to portray something<br>
>> that is value-preserving. What is the reason for calling it<br>
>> ‘description’?<br>
><br>
> The main reason was backward compatibility with Cocoa, which already has<br>
> a “description” property.<br>
><br>
>> Especially if NSObject subclasses won’t fit, then why not have a<br>
>> different method that can be strictly value preserving? (Then<br>
>> `description` can stay being an NSObject thing.)<br>
><br>
> --<br>
> Dave<br>
><br>
> _______________________________________________<br>
> swift-evolution mailing list<br>
> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>
</div></blockquote></div><br></div></div></div>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>