Timeline for Renaming options of custom functions while preserving backwards compatibility
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 5, 2018 at 12:45 | comment | added | Kuba | @MichaelE2 yes, probably. Will try to think about a workaround for this issue. | |
| Nov 5, 2018 at 12:13 | comment | added | Michael E2 |
I guess they did it to make processing {opts} convenient since Sequence[opts] is such an oxidizing agent. I use it fairly often when, say, writing a solver that needs to to call NDSolve with some user-supplied options and FindRoot with others. I was thinking that a user of a package might want to do the same. I had an idea based on one of halirutan's. Don't know if it's any good though.
|
|
| Nov 5, 2018 at 7:06 | comment | added | Kuba |
@MichaelE2 you mean w/wo {}? Yes, I was never a fan of OptionsPattern allowing them ;)
|
|
| Nov 5, 2018 at 2:38 | comment | added | Michael E2 |
foo[1, {"newName2" :> 1 + 2, "newName" -> 4}] works but foo[1, {"oldName2" :> 1 + 2, "oldName" -> 4}] does not.
|
|
| Nov 4, 2018 at 19:11 | history | answered | Kuba | CC BY-SA 4.0 |