Avoid matching on &Foo, when a plain Foo pattern works

The extra & in a pattern (match arm or if let) is unnecessary and only
makes the code harder to read. In most places it's enough to just
remove the & from the pattern, but in a few places a dereference (*)
needs to be added where the value captured in the pattern is used, as
removing the & changes the type of the captured value to be a
reference.

Overall, the changes are almost mechanical. Although the diff is huge,
it should be easy to read.

The clippy lint match_ref_pats warns about this. See:
https://rust-lang.github.io/rust-clippy/master/index.html#match_ref_pats

1 files changed, 3 insertions, 3 deletions

diff --git a/ipc/src/core.rs b/ipc/src/core.rs
index d6895e01..b4dd928a 100644
--- a/ipc/src/core.rs
+++ b/ipc/src/core.rs
@@ -291,9 +291,9 @@ pub enum IPCPolicy {
 impl<'a> From<&'a IPCPolicy> for u8 {
     fn from(policy: &IPCPolicy) -> Self {
         match policy {
-            &IPCPolicy::External => 0,
-            &IPCPolicy::Internal => 1,
-            &IPCPolicy::Robust => 2,
+            IPCPolicy::External => 0,
+            IPCPolicy::Internal => 1,
+            IPCPolicy::Robust => 2,
         }
     }
 }