-
Notifications
You must be signed in to change notification settings - Fork 127
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
feat(iterPipe): Add iterPipe
#520
base: master
Are you sure you want to change the base?
Conversation
*/ | ||
export function iterPipe<A, B>( | ||
values: IterableIterator<A>, | ||
op1: (value: A) => LazyResult<B> |
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.
question: we can also do
op1: (value: A) => LazyResult<B> | IterableIterator<B>
so we can write the example, where we include a function *
. i think it should be possible to tell this apart on runtime, it has hasNext
if it's a LazyResult, otherwise it's an IterableIterator
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit ba94f0a:
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #520 +/- ##
==========================================
+ Coverage 98.41% 98.44% +0.03%
==========================================
Files 127 136 +9
Lines 7954 8881 +927
Branches 724 766 +42
==========================================
+ Hits 7828 8743 +915
- Misses 123 135 +12
Partials 3 3 ☔ View full report in Codecov by Sentry. |
Why did you close the PR @cjquines ? |
@eranhirsch i couldn't find the convert to draft button oops. i'll reopen as a draft with some more fixes |
Should be on the right-side panel, somewhere near the reviewers box |
kinda closes #74
TODO:
Make sure that you:
src/index.ts
mapping.md
We use semantic PR titles to automate the release process!
https://conventionalcommits.org
PRs should be titled following using the format:
< TYPE >(< scope >)?: description
Available Types:
feat
: new functions, and changes to a function's type that would impact users.fix
: changes to the runtime behavior of an existing function, or refinements to it's type that shouldn't impact most users.perf
: changes to function implementations that improve a functions runtime performance.refactor
: changes to function implementations that are neitherfix
norperf
test
: tests-only changes (transparent to users of the function).docs
: changes to the documentation of a function or the documentation site.build
,ci
,style
,chore
, andrevert
: are only relevant for the internals of the library.For scope put the name of the function you are working on (either new or
existing).