<div dir="ltr">For what it's worth, you can accomplish a lot of assignment operator overload behavior via property get/set/willSet/didSet (similar to how Ruby methods suffixed with "=" are dispatched via dot notation), though it would require you to design your interface so that "=" is called on a property.<div><br></div><div>Stephen</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 7, 2015 at 9:15 AM, Don Wills 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">Thanks to all who replied. I apologize that my responses were disjoint - my spam checker delayed a couple of the messages until this morning.<br>
<br>
To those who suggested literal convertibles, I believe Stephen is correct in that it is insufficient to accomplish the semantics that I want with the syntax I had hoped for. It is about more than just initialization. I'll probably just use ":=" as the assignment operator. Not optimal, but it works.<br>
<span class="HOEnZb"><font color="#888888"><br>
Don<br>
</font></span><span class="im HOEnZb"><br>
> On Dec 6, 2015, at 11:59 AM, Stephen Celis <<a href="mailto:stephen.celis@gmail.com">stephen.celis@gmail.com</a>> wrote:<br>
><br>
> I think that his number assignment (via `<~`) depends on the current state of `amount`, and that using FloatLiteralConvertible does not provide enough information at the call site (since the current value is not available in the initializer).<br>
<br>
</span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">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>