lemmyg

4 ms·

1. 1.▲
   by lemmyg 8y ago

   That's true. And I see the other example answers they have written do assume the pointer can be null, although the original class makes no indication of this. To make the question clearer they should have added a function on the origin
2. 2.▲
   by lemmyg 8y ago

   Move assignment has nothing to do with 'clearing fields' or whatever it's that the moved-to value steals what it can and leaves the moved from value in a valid but unspecified state. Notably, you should still be able to assig
3. 3.▲
   by lemmyg 8y ago

   Exposing Web APIs (e.g. DOM) to WASM and projecting them into native languages seems like it overlaps a lot with defining actual native API projections that would be shared between browser implementations. It doesn't read like this is
4. 4.▲
   by lemmyg 8y ago

   In general this looks great! I assume the reason why many functions take non-const pointers as arguments (rather than non-const references) is because it follows the google style guide? https://google.github.io/styleguide&#