Stephanie Wilde-Hobbs
Stephanie Wilde-Hobbs
@asterite yep.
@asterite it doesn't help. `writev` was a tangent.
We can reopen/discuss in the original issue if neccesary.
No `--release` means no optimisation: every operation loads to registers from the stack, does a compiler primitive then stores again. The simplest possible code generation from the IR. This means...
I think it can be removed, it's easy enough to bitshift it back if required.
It should either fail or override. Compiler warnings should be avoided.
Deprecations are the only kind of warnings the compiler should provide, imo. I've been working to make them less verbose too (I've stated my vision for the deprecations UX many...
I'd rather write a "good" `Promise` implementation and then have `Promise.all`/`Promise.first` etc. As far as i'm concerned the abstraction of a fiber with a return value, called a promise or...
@straight-shoota you could do it like that or you could use promises like this: ```cr Promise.all( Promise.new ->func, Promise.new ->func2 ) ``` which is both less verbose and more powerful...
and JS promises have no way to cancel them, we don't need cancellation for them