-
Notifications
You must be signed in to change notification settings - Fork 1k
Open
Labels
breaking-changeissues whose solution would require breaking existing behaviorissues whose solution would require breaking existing behavior
Description
R itself recently started exporting a %notin% operator:
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, andweatherOz; the first two for re-exporting. Any clever tricks (à lacedta?) we might use so that interactive users who would getbase::`%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 useif (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.
jangorecki
Metadata
Metadata
Assignees
Labels
breaking-changeissues whose solution would require breaking existing behaviorissues whose solution would require breaking existing behavior