Conversation
| /// Raw display handle for the Web. | ||
| #[non_exhaustive] | ||
| #[derive(Debug, Clone, Copy, PartialEq, Eq, Hash)] | ||
| pub struct WebDisplayHandle {} |
There was a problem hiding this comment.
I just realized, an option that might make sense, even semantically, could be to include the transfer function in the display handle? WDYT?
There was a problem hiding this comment.
The last update was that its almost impossible to represent a transfer function properly, regardless of where its stored.
Do you have a specific representation in mind?
There was a problem hiding this comment.
I was thinking that if wasm-bindgen decides that it wants multiple tables, like you write in #185 (comment), then we might be able to store that table transfer function in a WasmBindgenDisplayHandle.
There was a problem hiding this comment.
I guess the question is also somewhat: Should we rename the WebDisplayHandle as well?
2 participants
Discussed in #185.