> On Oct 7, 2016, at 2:38 PM, Michael Gottesman via swift-dev
> <swift-dev@swift.org> wrote:
>
> Attached below is an updated version of the proposal. Again a rendered
> version is located at:
>
> https://gottesmm.github.io/proposals/high-level-arc-memory-operations.html
> <https://gottesmm.github.io/proposals/high-level-arc-memory-operations.html>
>
> Michael
This looks great Michael, a couple of comments/questions:
typo: affects -> effects.
>If ARC Code Motion wishes to move the ARC semantics of ownership qualified
>load, store instructions, it must now consider read/write effects. On the
>other hand, it will be able to now not consider the side-effects of
>destructors when moving retain/release operations.
Can you elaborate on what you mean by this? Does this mean the ARC optimizer
has additional freedom somehow to ignore side effects in deinits? What grants
that ability?
-Chris
_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev
