<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 22, 2016, at 9:30 PM, Brent Royal-Gordon <<a href="mailto:brent@architechies.com" class="">brent@architechies.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">float Point3DGetPointAtIndex(int idx, Point3D point)<br class="">__attribute__((swift_name("getter:subscript(_:self:)")))<br class="">void Point3DSetPointAtIndex(int idx, Point3D point, float val)<br class="">__attribute__((swift_name("getter:subscript(_:self:newValue:)")))<br class=""></blockquote><br class="">I think this is the best option. Subscripts can have multiple parameters, including parameter labels, so you need the full range of expressiveness, including `_`, to correctly represent them. `newValue`'s name is technically changeable, but it almost never actually *is* changed, and everyone will understand what it refers to.<br class=""></div></div></blockquote></div><div class=""><br class=""></div>Right. And at worse we’ve eliminated the ability to express<div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><font face="Menlo" class="">subscript (newValue newValue: Int) -> Int { … }</font></div></blockquote><div class=""><br class=""><div class="">I can live with that limitation.</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div class=""><br class=""></div></div></body></html>