-
-
Couldn't load subscription status.
- Fork 19.2k
Closed
Labels
Duplicate ReportDuplicate issue or pull requestDuplicate issue or pull requestGroupbyReshapingConcat, Merge/Join, Stack/Unstack, ExplodeConcat, Merge/Join, Stack/Unstack, Explode
Description
In the current implementation apply calls func twice on the first column/row to decide whether it can take a fast or slow code path. This can lead to unexpected behavior if func has side-effects, as they will take effect twice for the first column/row.
In my opinion apply() should have an option to disable this check. Sometimes for functions with side effects, consistent behaviour is more important that speed.
Metadata
Metadata
Assignees
Labels
Duplicate ReportDuplicate issue or pull requestDuplicate issue or pull requestGroupbyReshapingConcat, Merge/Join, Stack/Unstack, ExplodeConcat, Merge/Join, Stack/Unstack, Explode