Closed ponytailer closed 1 year ago
Is there a reason to call it of
over the more obvious name of chain
?
Is there a reason to call it
of
over the more obvious name ofchain
?
Haha,the same as java stream naming
Makes sense, although in the context of python I'd prefer chain
, particularly given its basically doing what itertools.chain
does :).
I'd also make the docstring a bit more clear, something like: "Chain the two iterators together into a new seq"
With those changes, I'd accept the PR, thanks!
Makes sense, although in the context of python I'd prefer
chain
, particularly given its basically doing whatitertools.chain
does :).I'd also make the docstring a bit more clear, something like: "Chain the two iterators together into a new seq"
With those changes, I'd accept the PR, thanks!
I rename the function.
@artemisart Thanks for your review.
LMK when you're done making changes and I can do another pre-merge review :)
LMK when you're done making changes and I can do another pre-merge review :)
I think it's done. Maybe should update the black
?
(pyfunctional-py3.10) ➜ ~/github/PyFunctional git:(master) black --version
black, 23.3.0 (compiled: no)
Python (CPython) 3.10.9
(pyfunctional-py3.10) ➜ ~/github/PyFunctional git:(master) black functional --check
All done! ✨ 🍰 ✨
13 files would be left unchanged.
(pyfunctional-py3.10) ➜ ~/github/PyFunctional git:(master) gt
On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean
Patch coverage: 100.00
% and project coverage change: +0.01
:tada:
Comparison is base (
e5eb3d3
) 98.08% compared to head (bd3878a
) 98.09%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
@EntilZha