On Tuesday, May 19, 2020 2:48:20 PM CDT you wrote: > I don't like this idea. The history of this provision is that I gave a CFJ > judgement essentially establishing something like this. Everyone > (especially G.) thought it was a terrible idea, and they persuaded me. CAN > has a very sensible default meaning currently, that allows us to do things > like specifying a method in one place and enabling its use in another. > Also, the need to write out the by announcement makes you think about > whether that's actually what you want. But most of all, I just really don't > like making this implicit, even if it's explicitly defined as being > implicit.
Do you happen to know whenabouts that discussion happened? I'd like to look at the arguments from then. What are the instances when it's useful to do something in a way besides announcement? My current though is that if we do things by announcement most of the time, and it's the safer way to do things, then it should be the enforced default and you should have to explicitly override it. -- nch
