<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Dec 4, 2017, at 12:12 PM, Vladimir.S via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><div class=""><div class=""><br class="">Probably the correct way to have dynamic calls in Swift is to 'mark' such code with special flag and we need to find it. For example:<br class=""><br class="">> // Python: d = np.array([1, 2, 3], dtype="i2")<br class="">> // Future Swift: let d = np.@array([6, 7, 8], dtype: "i2")<br class="">> // Future Swift: let d = np@array([6, 7, 8], dtype: "i2")<br class="">> // Future Swift: let d = np:array([6, 7, 8], dtype: "i2")<br class="">> // Future Swift: let d = np.~array([6, 7, 8], dtype: "i2")<br class="">> // Future Swift: let d = np.@array([6, 7, 8], dtype: "i2")<br class="">> // Future Swift: let d = np."array"([6, 7, 8], dtype: "i2") // name of dynamic method is like just string, no any guarantee & we can have any needed symbol in string to express the details of target dynamic language(if needed)<br class="">> // etc<br class=""><br class="">Yes, IMO such code should be second class citizen in Swift.<br class=""></div></div></blockquote></div><br class=""><div class="">This idea was discussed extensively upthread, and has been specifically addressed in the proposal:</div><div class=""><a href="https://gist.github.com/lattner/b016e1cf86c43732c8d82f90e5ae5438#increasing-visibility-of-dynamic-member-lookups" class="">https://gist.github.com/lattner/b016e1cf86c43732c8d82f90e5ae5438#increasing-visibility-of-dynamic-member-lookups</a></div><div class=""><br class=""></div><div class="">-Chris</div><div class=""><br class=""></div></body></html>