Joe Groff
That isn't valid `[let ]` syntax anymore. Did you mean: ``` factor [ 10 ] [ 0 '[ [let 10 :> A A _ + ] ] call( -- x...
locals and fry both need the retain stack and don't know about each other, so it makes sense that they wouldn't interoperate. This probably can't be fixed short of integrating...
> In swift 3, a closure was (IIRC) two pointers, a data handle for the closure and a pointer to code to get executes. Sometime between swift 3 and 4...
Yes, you can pass the context word to the invocation function in the `self` register (`r13` for x86-64). Both of these words are directly available in the closure value, and...
Overloading is a bad idea to begin with in general, so if there's a way to get the intended API effect with only one overload, I would suggest that no...
Windows still only comes with an OpenGL 1.1 implementation unless your graphics driver provides an ICD. You all might want to look into using ANGLE or some other portable OpenGL...
> I asked @jrose-apple, who suggested that one short-term alternative is to standardize all swiftcall functions to take only one extra parameter: > > void closure(void* arg1, void* arg2, void**...
@zhouwei For witness table entry points, there is still a consistent calling convention that all witnesses use. That logic duct tapes over some representation issues in SIL; they should end...
> Given the newness of WASM, it would be nice to instead see if support for this can be added to WASM; the feature is useful and could eventually benefit...