Also maybe let's not push behavior changes two days before release�� one of the proposed changes to not fire announcement when the object has changed would actually break things�� changes need some time to trigger all the bugs. :) After all the smallest changes usually have the highest bugrate, because when you go fast it's easy to not realize / forget corner cases.

Peter

On Sun, May 8, 2016 at 10:01 AM, stepharo <stepharo@free.fr> wrote:

Hi stefan

Should we apply that for all the announcements?
Do you write tests for this?
Stef

Why does every NewValueHolder have its own announcer?

And is initializing all those unused valueHolders in initialize
of Spec presentation classes not slow?

Talking to Latsabben on Slack, first step:

Name: SLICE-Issue-18167-NewValueHolder-classvalue-should-use-rawValue-StephanEggermont.1
Author: StephanEggermont
Time: 5 May 2016, 11:55:36.083109 am
UUID: d89767d0-5d9d-40b8-ad67-5887b22a338f
Ancestors:
Dependencies: NewValueHolder-StephanEggermont.34

Do not send announcements when you know there can't be any subscriptions