Stephanie Wilde-Hobbs
Stephanie Wilde-Hobbs
@straight-shoota No, `.all` and `.first` can easily take arrays.
Ah I see what you want. We could easily add block-based versions of `Promise.first` and `Promise.all` which do what you want, but I can't help but feel that adding tasks...
I was thinking more of a ```cr Promise.all do |promises| promises
@straight-shoota yeah I like the concept I was just wondering if we could work it into the "promise" concept for simplicity.
I don't think a promise library in crystal would look anything at all like a JS promise library. `.then` isn't really required at all. Libraries should expose synchronous APIs, and...
@stakach ah, my terminology was all messed up. I'd like futures in the stdlib and promises perhaps can be a shard built on that.
I'm still not sure what the conceptual difference between a promise and future would be in crystal though
Well, regardless of the terminology what I want is a fiber which can return a value, and you can wait for it to complete with a value or error
I think that `HTTP` needs a ground-up clean API redesign (without looking at the current API, the implementation is fine). It has collected a lot of issues which need to...
There's a workaround used in `Atomic(T)` [here](https://github.com/crystal-lang/crystal/blob/857743a1f2dc885fb4dd0fd40623d90cfd5d9388/src/atomic.cr#L13). A nicer syntax would probably be useful though.