> On Jul 2, 2016, at 12:14 PM, Nikita Leonov via swift-evolution > <[email protected]> wrote: > > I was trying to find what cause to not define static curried functions for > variables and constants and was not able to find a good reason.
In brief: This has been deferred until after Swift 3. We want to be able to provide read-write access to read-write properties, but Swift can't do that yet. (And at this point in Swift's release cycle, we're not really accepting new features unless they have very large source compatibility impacts, which this change wouldn't.) Here's one previous discussion from December: <https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151214/003008.html> If you want to look at more discussions on this topic, "lens" is a good keyword, although it'll also pick up some unrelated stuff. <https://www.google.com/?client=safari#q=lens+site:lists.swift.org> Hope this helps, -- Brent Royal-Gordon Architechies _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
