Planning Update June 23 & 30 -- Bugzilla to GitHub; Deprecations

[Nick Treleaven]

On Tuesday, 4 July 2023 at 13:25:06 UTC, FeepingCreature wrote:
> For instance, I got `alias Nullable.get this` deprecated and 
> later removed. I'm extremely glad that source of bugs is gone 
> and would be upset if it was reverted.

Thanks, me too. For that there was a simple migration path. I 
think the level of breakage has to be outweighed by the benefits 
of the change. Accidental bugs can be much more costly than 
having to add `.get` in a few places.

> What about things that are straight up bugs that contradict the 
> spec? For instance, you used to be able to access a private 
> function if it was overloaded with a public function that came 
> after. Should we write *that* in the spec? Or should we just 
> silently do the wrong thing?

For that example, it seems clear the user's code was at fault if 
it relied on accessing a private function. Though occasionally 
the spec may be wrong in some aspect - the solution may depend on 
how people understand the feature to work.