On Mon, Dec 21, 2015 at 11:55 AM, Chris Lattner via swift-evolution <
[email protected]> wrote:

> …there probably has to be some way to unsafely “force a call to a non-pure
> function to be allowed in a pure one”, both because of type system
> limitations as well as interoperability with C and other languages.  Even
> ignoring issues around errno, it would be sad for a pure function to not be
> able to call “sin(x)” just because it weren’t marked __attribute__((const)).
>

Minor tangent, but should the same apply to @noescape? (Lack of this is why
I bothered with SE-0012
<https://github.com/apple/swift-evolution/blob/master/proposals/0012-add-noescape-to-public-library-api.md>
)

Jacob
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to