That is: references inside those objects just don’t exist. Consequences include: you can’t use Vec<_> inside those objects: instead you use SAFEARRAY or CFArray or whatever. You can’t use String: use BSTR or CFString. Etc.
-
-
Show this thread
-
This is basically how all COM-like systems work anyway. They don’t generally use raw C strings and C arrays, they always create their own types.
Show this thread
End of conversation
New conversation -
-
-
Create a sane new dom api in rust that is implemented under the covers using the old dom. It would be great to allow javascript opt into the new apis in a safe, sandboxed way too
-
no javascript confirm, no synchronous blocking calls like localstorage, the only dom manipulation api is "replace this node subtree with this other node subtree" and the js gets a callback once it is swapped, etc
End of conversation
New conversation -
-
-
With ObjC you can build a wall around NSCopying types by defensively copying at the FFI edges. This is how Swift preserves value semantics/exclusivity to its own containers while bridging to the Cocoa ones
-
Hey Joe, an irrelevant question, could you tell me why NSInputStream does not support copying?
- 1 more reply
New conversation -
-
-
The thing I don't understand is how to put down an abstraction barrier that doesn't end up with a serialization cost every time you cross it.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.