Benno Stein

I worked on this a bunch this afternoon, but think we're better off keeping things as they are -- static functions that take a context argument are nice in client...

Our current setup has an interface `EagerCollection` in `skipruntime-ts/api` and an implementation `EagerCollectionImpl` in `skipruntime-ts/wasm`. (and analogous for lazy) Adding the static method to the implementation class is easy; the...

Because all of the implementation detail depends on wasm/FFI stuff which we don't want to include in the api package, but we definitely do need the interface there.

Doesn't matter to me! (I tend to just use gmail everywhere and not change repo-to-repo)

> With (arg1, arg2) => obj.method(arg1, arg2), I want to simplify to just obj.method and then it fails... so obj.method.bind(obj), although ugly, makes it explicit I've had the same impulse...

and the following, once #686 lands * `@skiplang/std` * `@skiplang/json` * `@skip-wasm/std` * `@skip-wasm/json` * `@skip-wasm/date`

That type does include non-object inhabitants in general: null, number, boolean, etc. Does the case you have in mind have some other constraint that `T` is an object type? If...

Looking again here, I believe the error is not because `T & DepSafe` isn't understood as an object type but actually because Typescript doesn't know that `vals.toArray()` is non-empty, so...

> The skipruntime test is flaky, rerunning it passed. I suspect a race like the one Lucas hit -- working on some fixes to make them more robust to timing...

In the example I'm working with (running the hackernews example containers under kubernetes) all of the runService calls are awaited, but no message is printed without this patch. I'll see...