> If it mutates whatever the input is referencing, it would have a side-effect which makes it "not pure" (for my understanding of what “pure” means).
I am not really sure of it (I have not played around with it until now) but I don't think that this is an issue with the swift inout, cf. https://developer.apple.com/library/content/documentation/Swift/Conceptual/Swift_Programming_Language/Declarations.html#//apple_ref/doc/uid/TP40014097-CH34-ID545 Nicolas On Thu, Feb 16, 2017 at 8:55 PM, David Sweeris via swift-evolution < [email protected]> wrote: > > > On Feb 16, 2017, at 11:27 AM, Sean Heber via swift-evolution < > [email protected]> wrote: > > > > Doesn’t this break down if you can pass a reference as a parameter to a > pure function? If that’s not allowed, I guess I must have missed it. Also > this seems to require the function has a return value. I suppose generally > a pure function without a return value wouldn’t make much sense - unless > you pass it a reference. > > If it mutates whatever the input is referencing, it would have a > side-effect which makes it "not pure" (for my understanding of what “pure” > means). > > - Dave Sweeris > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
