8000 Add Sync & Async instances for Iterant by oleg-py · Pull Request #600 · monix/monix · GitHub
[go: up one dir, main page]

Skip to content

Add Sync & Async instances for Iterant - #600

Merged
alexandru merged 1 commit into
monix:masterfrom
oleg-py:iterant-sync
Feb 28, 2018
Merged

alexandru merged 1 commit into
monix:masterfrom
oleg-py:iterant-sync

Conversation

@oleg-py
@oleg-py oleg-py commented Feb 25, 2018
Copy link
Copy Markdown
Collaborator

Closes #599

I went ahead and implemented Async instance too (under the assumption that callback will only be invoked once, so it just delegates to underlying F). Couldn't do Effect though in a similar way, because signature of runAsync sort-of implies cardinality of 1.

@oleg-py
oleg-py commented Feb 27, 2018
Copy link
Copy Markdown
Collaborator Author

@alexandru not sure why build fails, could you please take a look?

@alexandru
Copy link
Copy Markdown
Member

The build is timing out and it can do so in a piece of logic that wasn't timing out before, possibly due to the CPU being very busy (although I don't understand how, because I remember that I disabled testing in parallel, but those settings never worked properly anyway).

The tests for AsyncLaws and SyncLaws might break Travis. We might need to adjust the ScalaCheck parameters in those tests, to generate shorter Iterant values.

@alexandru
alexandru merged commit 5bd360b into monix:master Feb 28, 2018
@alexandru
Copy link
Copy Markdown
Member

One problem are all the stack-safety checks in SyncLaws, which on Travis are a problem due to the limited CPU available.

@alexandru
Copy link
Copy Markdown
Member

The attempted fix was to disable them when running on top of Travis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0