Hi Levente,


please ignore my previous message, I should have read this one first. :-) I think a problem with tests is that in our usual workflow, they will be ignored until it's release time again. This is why I would hesitate to use them for defining any kind of coding style or guideline, their feedback cycle is much more indirect than an immediate DeprecationWarning. If we really cannot deprecate #ifNotNilDo: in the common way, what about something like #trunkDeprecated: which only raises a warning if the sender is located in a Trunk package? Or would this be too slow?


Best,

Christoph

________________________________
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von Levente Uzonyi <leves at caesar.elte.hu>
Gesendet: Freitag, 3. September 2021 20:42:56
An: The general-purpose Squeak developers list
Betreff: [squeak-dev] Deprecating #ifNotNilDo: & friends

Hi All,

We already have #ifNotNil: which has been doing the same thing as
#ifNotNilDo: for about 10 years now.
The idea is to deprecate #ifNotNilDo: softly, without raising a warning on
usage just like how it's done with #doWithIndex:.
The inbox entries 60Deprecated-ul.96 and Kernel-ul.1409 contain the
necessary changes, while KernelTests-ul.405 has an additional test to
verify that no methods use #ifNotNilDo:.


Levente

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210903/6db46227/attachment.html>