+1 "In the end, we will remember not the words of our enemies, but the silence of our friends." -- Martin Luther King
Remko. On Fri, Jun 12, 2020 at 2:17 AM Adam L. Davis <adam...@gmail.com> wrote: > +1 > > On Thu, Jun 11, 2020 at 12:12 PM Søren Berg Glasius <soe...@glasius.dk> > wrote: > > > > +1 > > > > Best regards / Med venlig hilsen, > > Søren Berg Glasius > > > > Hedevej 1, Gl. Rye, 8680 Ry, Denmark > > Mobile: +45 40 44 91 88, Skype: sbglasius > > --- Press ESC once to quit - twice to save the changes. > > > > > > Den tor. 11. jun. 2020 kl. 16.50 skrev Paul King <pa...@asert.com.au>: > >> > >> Hi folks, > >> > >> Given recent world events, there are numerous projects that are taking > the opportunity to use more inclusive terminology especially in names > within APIs. E.g. getting rid of things like master/slave, > blacklist/whitelist, etc. While I have never witnessed any racist behavior > in the Groovy community, it seems worthwhile to be as inclusive as we can. > I scanned our codebase and it seems that the only potential candidate we > have for such a change would be in SecureASTCustomizer. But feel free to > chime in if you think there are others. > >> > >> For backwards compatibility, I wouldn't propose to remove the old names > in the first instance, just provide friendly aliases. We can deprecate > and/or remove the current names later if we feel the need. Some example > aliases could be something like: > >> > >> tokensWhitelist => allowedTokens > >> staticStarImportsWhitelist => allowedStaticStarImports > >> importsBlacklist => prohibitedImports (or disallowedImports) > >> > >> Thoughts? > >> > >> Cheers, Paul. > >> > > > -- > Adam Davis > Web: github.adamldavis.com >
