You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assuming JuliaLang/julia#46453 gets merged at some point, Base will export functions insert and delete. This raises the question of what to do with Accessors.insert and delete? At least three possible alternatives:
Keep as-is: separate functions with the same name. They'll need to be qualified then, and writing Accessors.delete(...) is pretty verbose.
Add new methods to Base functions. The current convenience remains, with minor type piracy like delete(_, ::ComposedFunction). Hard to imagine something other than optics library defining this method anyway :)
Change their names to something different. Hard to come up with similarly clean names. odelete?
I wonder if I'm missing others or their +/-.
The text was updated successfully, but these errors were encountered:
aplavin
changed the title
insert and delete after these functions get into Base
fate of insert and delete after these functions get into Base
Aug 27, 2023
Assuming JuliaLang/julia#46453 gets merged at some point, Base will export functions
insert
anddelete
. This raises the question of what to do withAccessors.insert
anddelete
? At least three possible alternatives:Accessors.delete(...)
is pretty verbose.delete(_, ::ComposedFunction)
. Hard to imagine something other than optics library defining this method anyway :)odelete
?I wonder if I'm missing others or their +/-.
The text was updated successfully, but these errors were encountered: