msg_socket_on_derive: use fully qualified types

The types from msg_socket were assumed to be in scope for the custom
derive implementation, which would cause mysterious compiler errors if
the custom derive was invoked in a module without msg_socket types in
scope.

This CL uses fully qualified types in the generated output to avoid
these errors.

This change also uses `extern crate msg_socket` in case the call site
doesn't have it in scope.

BUG=None
TEST=cargo test -p msg_on_socket_derive

Change-Id: Ie6443cd4ffc070d27e71de123090a58f19846472
Reviewed-on: https://chromium-review.googlesource.com/1314208
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Jingkui Wang <jkwang@google.com>

1 files changed, 23 insertions, 0 deletions

diff --git a/msg_socket/tests/tuple.rs b/msg_socket/tests/tuple.rs
new file mode 100644
index 0000000..717cd91
--- /dev/null
+++ b/msg_socket/tests/tuple.rs
@@ -0,0 +1,23 @@
+extern crate msg_on_socket_derive;
+extern crate msg_socket;
+extern crate sys_util;
+
+use sys_util::EventFd;
+
+use msg_socket::*;
+
+#[derive(MsgOnSocket)]
+struct Message(u8, u16, EventFd);
+
+#[test]
+fn sock_send_recv_tuple() {
+    let (req, res) = pair::<Message, Message>().unwrap();
+    let e0 = EventFd::new().unwrap();
+    let e1 = e0.try_clone().unwrap();
+    req.send(&Message(1, 0x12, e0)).unwrap();
+    let r = res.recv().unwrap();
+    assert_eq!(r.0, 1);
+    assert_eq!(r.1, 0x12);
+    r.2.write(0x0f0f).unwrap();
+    assert_eq!(e1.read().unwrap(), 0x0f0f);
+}