R itself recently started exporting a %notin% operator:
https://github.com/r-devel/r-svn/blob/80be987b9999121e8b9f371562c5b61356a2e25a/src/library/base/R/match.R#L40
That collides with our own %notin%:
@aitap in #7446 mentioned some ideas for this deprecation process, which will be new to us:
Three CRAN packages import %notin%: bruceR, tidyfst, and weatherOz; the first two for re-exporting. Any clever tricks (à la cedta?) we might use so that interactive users who would get base::`%notin%` anyway will not get penalised? I see that some packages (e.g. backports) export objects conditionally on R version. Should we try to eventually use if (getRversion() < "4.6.0")) export("%notin%") and similarly emit deprecation warnings only on R ≥ 4.6.0?
I would like to see R commit to including it in a release before we do anything too drastic.
R itself recently started exporting a
%notin%operator:https://github.com/r-devel/r-svn/blob/80be987b9999121e8b9f371562c5b61356a2e25a/src/library/base/R/match.R#L40
That collides with our own
%notin%:@aitap in #7446 mentioned some ideas for this deprecation process, which will be new to us:
I would like to see R commit to including it in a release before we do anything too drastic.