How you could somewhat rebase manually (to understand the effect; or because you like to handle the merge conflicts more granular or be more selective):
We assume we have the branch “Feat” which was started on an old version of “Main”, and now want to rebase it:
- Rename “Feat” to “Old” (does not happen during rebase, but we kinda need it for this demonstration)
- Create “Feat” at the newest (or wherever you want) commit of “Main”
- Cherrypick all commits from “Old” into “Feat”
Et viola - you kinda manually rebased “Feat” on “Main”
the is_even package does not provide much worth indeed because it simply negates is_odd and thereby all its benefit.
It’s dependency is_odd on the other hand provides at least some additional checks (it also checks if the value is a valid integer below the max int value)
And while I would indeed see uses for such methods (especially with the other checks, no simple oneliners) in some cases, especially in testing: This is stuff you write yourself, throw it in a e.g. NumberUtils class and everything is fine. You do never depend on an external library for that. The benefit (not spending a few seconds to write it) does not outweigh any of the drawbacks that come with external libraries.