[swift-evolution] Proposal: Introduce User-defined "Dynamic Member Lookup" Types

[Ondrej Barina]

+1 for the proposal

Ondrej Barina

On Tue, Dec 5, 2017 at 3:16 PM, BJ Homer via swift-evolution <
swift-evolution at swift.org> wrote:

>
>
> On Dec 5, 2017, at 7:06 AM, Tino Heth via swift-evolution <
> swift-evolution at swift.org> wrote:
>
>
> Also, I don’t think anything can prevent all abuses (it’s an subjective
> classification anyways) — people might just use PyVals because dynamic
> behavior, and that would imho be a huge abuse.
>
>
> Can you give an example of how someone would use such a PyVal to do
> something other than interoperate with Python? I’m having trouble imagining
> what your concern is.
>
> Specifically in the case of PyVal, I imagine it would already be
> hard-coded to call into Python for any dynamic lookup, so I don’t see how
> one could use “just use PyVal because dynamic behavior”. Are you saying
> that someone would just write all their code in a Python library, and then
> call into it from Swift?
>
> -BJ
>
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20171205/4625f45a/attachment.html>