Mojo custom type mapping: support move-only types |
|
Issue descriptionCurrently, generated bindings code always passes native types as const reference. That doesn't work in some cases, for example: - a native type contains a Mojo interface request that needs to be taken by the serialization code; - user code would like to take ownership of received objects of the native type, in order to avoid unnecessary copies. |
|
►
Sign in to add a comment |
|
Comment 1 by yzshen@chromium.org
, Aug 26 2016Status: Fixed (was: Untriaged)