-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
depr(python,rust!): Deprecate str.explode
in favor of str.split("").explode()
#16508
Conversation
str.explode
str.explode
in favor of str.split("").explode()
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #16508 +/- ##
==========================================
- Coverage 81.53% 81.52% -0.02%
==========================================
Files 1410 1410
Lines 185061 184948 -113
Branches 2982 2984 +2
==========================================
- Hits 150885 150772 -113
Misses 33660 33660
Partials 516 516 ☔ View full report in Codecov by Sentry. |
CodSpeed Performance ReportMerging #16508 will degrade performances by 15.56%Comparing Summary
Benchmarks breakdown
|
split = self.split("") | ||
return F.when(split.ne_missing([])).then(split).otherwise([""]).explode() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This replaces the existing functionality until it is removed completely.
Closes #14605
It's a bit of an odd function that makes less sense now that our string representation no longer has offsets.
Users should use
str.split("").explode()
instead.