On Tue, Feb 23, 2016 at 8:17 PM, stepharo <[email protected]> wrote: > I do not think that Pharo will become a static language :) > For the moment we can let it as a documentation. > Now I would prefer to have tests because such annotations may be obsolete.
Maybe not if those pragmas become *active* when the unit tests are run. Then they might be treated like asserts without application runtime penalty. The benefit over unit tests for package A, would be these asserts would be active when called from the unit tests of package B. (??) cheers -ben
