Nikos Kalogridis

I see, at least in modern vms though there is a clear advantage on using native functions instead of loops https://jsperf.com/array-for-loops-vs-slice/1 I could make a complete test for this prelude...

@davidchase not at all. I was just browsing through the code and I was impressed that it used for loops for manipulating arrays. I have recently also noticed myself that...

I think it would be a good idea to add two more functions on the VirtualTimer: ``` start(): void stop(): void ``` Thoughts?

interesting that the eslint directive was affecting standard .... anyway fixed it by reordering imports. @briancavalier what is the reason of implementing curry inside the core/src/index.js and not exporting the...

In order to not leave this PR pending while discussing I propose to open an issue for discussing the curry in the API or module boundary. So I reverted the...

Initial implementation is complete codewise, documentation is still pending

My initial goal was to expose the helper functions inside the `@most/core` in order to be usable for testing outside of the `@most/core` package. I think its a great idea...

you can have a look at #231 typescript typing file to get an idea of what the api is going to be up to now. Since its the first time...

I agree that `@most/test` should be minimal and intuitive. As I see it, it needs to provide: 1. Mocked stream creation functions (ie. atTimes, makeEventsFromArray, makeEvents, etc) 1. an API...

one idea for collectEventsFor is to rename it to collectEvents and provide a chained method of building execution. ie ```js collectEvents .from(source) .fromTime(4) .upToTime(6) .then(...) ``` or something like ```js...