Can I borrow a slice from a custom type?











up vote
0
down vote

favorite












It's possible to borrow a Vec<u32> into either a &Vec<u32> or a &[u32]. I thought this was thanks to either the AsRef or Borrow traits. However, I was unable to implement such borrowing on my own custom type. Am I barking up the wrong tree here?



use std::borrow::Borrow;

struct MyArray([u32; 5]);

impl MyArray {
fn new() -> MyArray {
MyArray([42; 5])
}
}

impl AsRef<[u32]> for MyArray {
fn as_ref(&self) -> &[u32] {
&self.0
}
}

impl Borrow<[u32]> for MyArray {
fn borrow(&self) -> &[u32] {
&self.0
}
}

fn main() {
let ma = MyArray::new();
let _: &[u32] = &ma; // compilation failure
}









share|improve this question




























    up vote
    0
    down vote

    favorite












    It's possible to borrow a Vec<u32> into either a &Vec<u32> or a &[u32]. I thought this was thanks to either the AsRef or Borrow traits. However, I was unable to implement such borrowing on my own custom type. Am I barking up the wrong tree here?



    use std::borrow::Borrow;

    struct MyArray([u32; 5]);

    impl MyArray {
    fn new() -> MyArray {
    MyArray([42; 5])
    }
    }

    impl AsRef<[u32]> for MyArray {
    fn as_ref(&self) -> &[u32] {
    &self.0
    }
    }

    impl Borrow<[u32]> for MyArray {
    fn borrow(&self) -> &[u32] {
    &self.0
    }
    }

    fn main() {
    let ma = MyArray::new();
    let _: &[u32] = &ma; // compilation failure
    }









    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      It's possible to borrow a Vec<u32> into either a &Vec<u32> or a &[u32]. I thought this was thanks to either the AsRef or Borrow traits. However, I was unable to implement such borrowing on my own custom type. Am I barking up the wrong tree here?



      use std::borrow::Borrow;

      struct MyArray([u32; 5]);

      impl MyArray {
      fn new() -> MyArray {
      MyArray([42; 5])
      }
      }

      impl AsRef<[u32]> for MyArray {
      fn as_ref(&self) -> &[u32] {
      &self.0
      }
      }

      impl Borrow<[u32]> for MyArray {
      fn borrow(&self) -> &[u32] {
      &self.0
      }
      }

      fn main() {
      let ma = MyArray::new();
      let _: &[u32] = &ma; // compilation failure
      }









      share|improve this question















      It's possible to borrow a Vec<u32> into either a &Vec<u32> or a &[u32]. I thought this was thanks to either the AsRef or Borrow traits. However, I was unable to implement such borrowing on my own custom type. Am I barking up the wrong tree here?



      use std::borrow::Borrow;

      struct MyArray([u32; 5]);

      impl MyArray {
      fn new() -> MyArray {
      MyArray([42; 5])
      }
      }

      impl AsRef<[u32]> for MyArray {
      fn as_ref(&self) -> &[u32] {
      &self.0
      }
      }

      impl Borrow<[u32]> for MyArray {
      fn borrow(&self) -> &[u32] {
      &self.0
      }
      }

      fn main() {
      let ma = MyArray::new();
      let _: &[u32] = &ma; // compilation failure
      }






      rust






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 11 at 16:50









      Shepmaster

      145k11274408




      145k11274408










      asked Nov 11 at 16:37









      Michael Snoyman

      27.5k23466




      27.5k23466
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          3
          down vote



          accepted










          You are looking for std::ops::Deref:




          In addition to being used for explicit dereferencing operations with the (unary) * operator in immutable contexts, Deref is also used implicitly by the compiler in many circumstances. This mechanism is called 'Deref coercion'. In mutable contexts, DerefMut is used.




          Modified code:



          use std::ops::Deref;

          struct MyArray([u32; 5]);

          impl MyArray {
          fn new() -> MyArray {
          MyArray([42; 5])
          }
          }

          impl Deref for MyArray {
          type Target = [u32];

          fn deref(&self) -> &[u32] {
          &self.0
          }
          }

          fn main() {
          let ma = MyArray::new();
          let _: &[u32] = &ma;
          }





          share|improve this answer























          • Related: Is it considered a bad practice to implement Deref for newtypes?.
            – Shepmaster
            Nov 11 at 16:51










          • That's exactly what I was missing, thank you!
            – Michael Snoyman
            Nov 11 at 17:04











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53250856%2fcan-i-borrow-a-slice-from-a-custom-type%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          3
          down vote



          accepted










          You are looking for std::ops::Deref:




          In addition to being used for explicit dereferencing operations with the (unary) * operator in immutable contexts, Deref is also used implicitly by the compiler in many circumstances. This mechanism is called 'Deref coercion'. In mutable contexts, DerefMut is used.




          Modified code:



          use std::ops::Deref;

          struct MyArray([u32; 5]);

          impl MyArray {
          fn new() -> MyArray {
          MyArray([42; 5])
          }
          }

          impl Deref for MyArray {
          type Target = [u32];

          fn deref(&self) -> &[u32] {
          &self.0
          }
          }

          fn main() {
          let ma = MyArray::new();
          let _: &[u32] = &ma;
          }





          share|improve this answer























          • Related: Is it considered a bad practice to implement Deref for newtypes?.
            – Shepmaster
            Nov 11 at 16:51










          • That's exactly what I was missing, thank you!
            – Michael Snoyman
            Nov 11 at 17:04















          up vote
          3
          down vote



          accepted










          You are looking for std::ops::Deref:




          In addition to being used for explicit dereferencing operations with the (unary) * operator in immutable contexts, Deref is also used implicitly by the compiler in many circumstances. This mechanism is called 'Deref coercion'. In mutable contexts, DerefMut is used.




          Modified code:



          use std::ops::Deref;

          struct MyArray([u32; 5]);

          impl MyArray {
          fn new() -> MyArray {
          MyArray([42; 5])
          }
          }

          impl Deref for MyArray {
          type Target = [u32];

          fn deref(&self) -> &[u32] {
          &self.0
          }
          }

          fn main() {
          let ma = MyArray::new();
          let _: &[u32] = &ma;
          }





          share|improve this answer























          • Related: Is it considered a bad practice to implement Deref for newtypes?.
            – Shepmaster
            Nov 11 at 16:51










          • That's exactly what I was missing, thank you!
            – Michael Snoyman
            Nov 11 at 17:04













          up vote
          3
          down vote



          accepted







          up vote
          3
          down vote



          accepted






          You are looking for std::ops::Deref:




          In addition to being used for explicit dereferencing operations with the (unary) * operator in immutable contexts, Deref is also used implicitly by the compiler in many circumstances. This mechanism is called 'Deref coercion'. In mutable contexts, DerefMut is used.




          Modified code:



          use std::ops::Deref;

          struct MyArray([u32; 5]);

          impl MyArray {
          fn new() -> MyArray {
          MyArray([42; 5])
          }
          }

          impl Deref for MyArray {
          type Target = [u32];

          fn deref(&self) -> &[u32] {
          &self.0
          }
          }

          fn main() {
          let ma = MyArray::new();
          let _: &[u32] = &ma;
          }





          share|improve this answer














          You are looking for std::ops::Deref:




          In addition to being used for explicit dereferencing operations with the (unary) * operator in immutable contexts, Deref is also used implicitly by the compiler in many circumstances. This mechanism is called 'Deref coercion'. In mutable contexts, DerefMut is used.




          Modified code:



          use std::ops::Deref;

          struct MyArray([u32; 5]);

          impl MyArray {
          fn new() -> MyArray {
          MyArray([42; 5])
          }
          }

          impl Deref for MyArray {
          type Target = [u32];

          fn deref(&self) -> &[u32] {
          &self.0
          }
          }

          fn main() {
          let ma = MyArray::new();
          let _: &[u32] = &ma;
          }






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 11 at 16:52









          Shepmaster

          145k11274408




          145k11274408










          answered Nov 11 at 16:50









          udoprog

          1,557914




          1,557914












          • Related: Is it considered a bad practice to implement Deref for newtypes?.
            – Shepmaster
            Nov 11 at 16:51










          • That's exactly what I was missing, thank you!
            – Michael Snoyman
            Nov 11 at 17:04


















          • Related: Is it considered a bad practice to implement Deref for newtypes?.
            – Shepmaster
            Nov 11 at 16:51










          • That's exactly what I was missing, thank you!
            – Michael Snoyman
            Nov 11 at 17:04
















          Related: Is it considered a bad practice to implement Deref for newtypes?.
          – Shepmaster
          Nov 11 at 16:51




          Related: Is it considered a bad practice to implement Deref for newtypes?.
          – Shepmaster
          Nov 11 at 16:51












          That's exactly what I was missing, thank you!
          – Michael Snoyman
          Nov 11 at 17:04




          That's exactly what I was missing, thank you!
          – Michael Snoyman
          Nov 11 at 17:04


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53250856%2fcan-i-borrow-a-slice-from-a-custom-type%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Xamarin.iOS Cant Deploy on Iphone

          Glorious Revolution

          Dulmage-Mendelsohn matrix decomposition in Python