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
A colleague of mine responded to a client email with the advice to run match_on first and pass that to fullmatch. There were no complications on the match that would benefit from this. I asked him how he arrived at that conclusion and he sent the following:
If you ?optmatch, it takes you to the object definition/summary. Then, the fullmatch doc is somewhat overwhelming on first pass. The def of the first argument 'x' refers to match_on, which I went to to simplify how many options were necessary.
Should we re-arrange/clean up the documentation of fullmatch to put the basic use cases (specifically I'm thinking fullmatch.formula) at the front?
The text was updated successfully, but these errors were encountered:
A colleague of mine responded to a client email with the advice to run
match_on
first and pass that tofullmatch
. There were no complications on the match that would benefit from this. I asked him how he arrived at that conclusion and he sent the following:Should we re-arrange/clean up the documentation of fullmatch to put the basic use cases (specifically I'm thinking
fullmatch.formula
) at the front?The text was updated successfully, but these errors were encountered: