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
See the original implementation where the processor function is only executed once if it's a known method.
I'm not sure if this is an optimization to prevent duplicate calls, or if multiple invocations could lead to some undesired state? i.e. the processor function is not idempotent.
The text was updated successfully, but these errors were encountered:
basically the current impl of extract_without_order doesn't double call the processors, but if the scorer calls processing, you're hosed. It just so happens the original scorers by default do because we havent split them out as concepts.
not quite, no. You have things like ratio_full which does processor and delegates to simple_ratio which could be considered a scorer, but that structure is not applied to, say, partial_ratio_full which would need to split out most of its body into a best_partial_ratio or something.
See the original implementation where the processor function is only executed once if it's a known method.
I'm not sure if this is an optimization to prevent duplicate calls, or if multiple invocations could lead to some undesired state? i.e. the processor function is not idempotent.
The text was updated successfully, but these errors were encountered: