Originally at 2015-01-19T12:25:30Z by Herbert Vojčík
Now that each package has different environment, moving a method between protocols may trigger a need for recompilation, if at least one of involved was extension method protocol.
This in fact needs review of existing code, maybe methods are already compiled when moved.
Originally at 2015-01-19T12:25:30Z by Herbert Vojčík
Now that each package has different environment, moving a method between protocols may trigger a need for recompilation, if at least one of involved was extension method protocol.
This in fact needs review of existing code, maybe methods are already compiled when moved.
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/7868133-moving-a-method-into-different-protocol-may-need-recompilation?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github).
</bountysource-plugin>
Originally at 2015-01-19T12:25:30Z by Herbert Vojčík
Now that each package has different environment, moving a method between protocols may trigger a need for recompilation, if at least one of involved was extension method protocol.
This in fact needs review of existing code, maybe methods are already compiled when moved.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.