Why is calling a FnOnce closure a move?










7














I'm trying to pass in a closure to a function that will then mutate something passed into it within the scope of the function. Based on my current understanding of Rust, that should look something like this:



pub fn call_something(callback: &FnOnce(&mut Vec<i32>)) 
let mut my_vec = vec![0, 1, 2, 3, 4];
callback(&mut my_vec);



That results in these errors:



error[E0161]: cannot move a value of type dyn for<'r> std::ops::FnOnce(&'r mut std::vec::Vec<i32>): the size of dyn for<'r> std::ops::FnOnce(&'r mut std::vec::Vec<i32>) cannot be statically determined
--> src/lib.rs:3:5
|
3 | callback(&mut my_vec);
| ^^^^^^^^

error[E0507]: cannot move out of borrowed content
--> src/lib.rs:3:5
|
3 | callback(&mut my_vec);
| ^^^^^^^^ cannot move out of borrowed content


Why is calling a FnOnce a move? What am I missing here?










share|improve this question




























    7














    I'm trying to pass in a closure to a function that will then mutate something passed into it within the scope of the function. Based on my current understanding of Rust, that should look something like this:



    pub fn call_something(callback: &FnOnce(&mut Vec<i32>)) 
    let mut my_vec = vec![0, 1, 2, 3, 4];
    callback(&mut my_vec);



    That results in these errors:



    error[E0161]: cannot move a value of type dyn for<'r> std::ops::FnOnce(&'r mut std::vec::Vec<i32>): the size of dyn for<'r> std::ops::FnOnce(&'r mut std::vec::Vec<i32>) cannot be statically determined
    --> src/lib.rs:3:5
    |
    3 | callback(&mut my_vec);
    | ^^^^^^^^

    error[E0507]: cannot move out of borrowed content
    --> src/lib.rs:3:5
    |
    3 | callback(&mut my_vec);
    | ^^^^^^^^ cannot move out of borrowed content


    Why is calling a FnOnce a move? What am I missing here?










    share|improve this question


























      7












      7








      7







      I'm trying to pass in a closure to a function that will then mutate something passed into it within the scope of the function. Based on my current understanding of Rust, that should look something like this:



      pub fn call_something(callback: &FnOnce(&mut Vec<i32>)) 
      let mut my_vec = vec![0, 1, 2, 3, 4];
      callback(&mut my_vec);



      That results in these errors:



      error[E0161]: cannot move a value of type dyn for<'r> std::ops::FnOnce(&'r mut std::vec::Vec<i32>): the size of dyn for<'r> std::ops::FnOnce(&'r mut std::vec::Vec<i32>) cannot be statically determined
      --> src/lib.rs:3:5
      |
      3 | callback(&mut my_vec);
      | ^^^^^^^^

      error[E0507]: cannot move out of borrowed content
      --> src/lib.rs:3:5
      |
      3 | callback(&mut my_vec);
      | ^^^^^^^^ cannot move out of borrowed content


      Why is calling a FnOnce a move? What am I missing here?










      share|improve this question















      I'm trying to pass in a closure to a function that will then mutate something passed into it within the scope of the function. Based on my current understanding of Rust, that should look something like this:



      pub fn call_something(callback: &FnOnce(&mut Vec<i32>)) 
      let mut my_vec = vec![0, 1, 2, 3, 4];
      callback(&mut my_vec);



      That results in these errors:



      error[E0161]: cannot move a value of type dyn for<'r> std::ops::FnOnce(&'r mut std::vec::Vec<i32>): the size of dyn for<'r> std::ops::FnOnce(&'r mut std::vec::Vec<i32>) cannot be statically determined
      --> src/lib.rs:3:5
      |
      3 | callback(&mut my_vec);
      | ^^^^^^^^

      error[E0507]: cannot move out of borrowed content
      --> src/lib.rs:3:5
      |
      3 | callback(&mut my_vec);
      | ^^^^^^^^ cannot move out of borrowed content


      Why is calling a FnOnce a move? What am I missing here?







      rust closures move-semantics






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 9 at 22:08









      Shepmaster

      147k11281415




      147k11281415










      asked Nov 9 at 22:01









      user96425

      382




      382






















          1 Answer
          1






          active

          oldest

          votes


















          7















          Why is calling a FnOnce a move?




          Because that's the definition of what makes a closure FnOnce:



          extern "rust-call" fn call_once(self, args: Args) -> Self::Output
          // ^^^^


          Contrast this to FnMut and Fn:



          extern "rust-call" fn call_mut(&mut self, args: Args) -> Self::Output
          // ^^^^^^^^^




          extern "rust-call" fn call(&self, args: Args) -> Self::Output
          // ^^^^^


          See also:



          • When does a closure implement Fn, FnMut and FnOnce?

          • "cannot move a value of type FnOnce" when moving a boxed function

          • Cannot move out of borrowed content


          You probably want



          pub fn call_something(callback: impl FnOnce(&mut Vec<i32>))


          or



          pub fn call_something<F>(callback: F)
          where
          F: FnOnce(&mut Vec<i32>),


          These are identical. They both take ownership of the closure, which means that you can call the closure and consume it in the process.






          share|improve this answer






















            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',
            autoActivateHeartbeat: false,
            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%2f53233803%2fwhy-is-calling-a-fnonce-closure-a-move%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









            7















            Why is calling a FnOnce a move?




            Because that's the definition of what makes a closure FnOnce:



            extern "rust-call" fn call_once(self, args: Args) -> Self::Output
            // ^^^^


            Contrast this to FnMut and Fn:



            extern "rust-call" fn call_mut(&mut self, args: Args) -> Self::Output
            // ^^^^^^^^^




            extern "rust-call" fn call(&self, args: Args) -> Self::Output
            // ^^^^^


            See also:



            • When does a closure implement Fn, FnMut and FnOnce?

            • "cannot move a value of type FnOnce" when moving a boxed function

            • Cannot move out of borrowed content


            You probably want



            pub fn call_something(callback: impl FnOnce(&mut Vec<i32>))


            or



            pub fn call_something<F>(callback: F)
            where
            F: FnOnce(&mut Vec<i32>),


            These are identical. They both take ownership of the closure, which means that you can call the closure and consume it in the process.






            share|improve this answer



























              7















              Why is calling a FnOnce a move?




              Because that's the definition of what makes a closure FnOnce:



              extern "rust-call" fn call_once(self, args: Args) -> Self::Output
              // ^^^^


              Contrast this to FnMut and Fn:



              extern "rust-call" fn call_mut(&mut self, args: Args) -> Self::Output
              // ^^^^^^^^^




              extern "rust-call" fn call(&self, args: Args) -> Self::Output
              // ^^^^^


              See also:



              • When does a closure implement Fn, FnMut and FnOnce?

              • "cannot move a value of type FnOnce" when moving a boxed function

              • Cannot move out of borrowed content


              You probably want



              pub fn call_something(callback: impl FnOnce(&mut Vec<i32>))


              or



              pub fn call_something<F>(callback: F)
              where
              F: FnOnce(&mut Vec<i32>),


              These are identical. They both take ownership of the closure, which means that you can call the closure and consume it in the process.






              share|improve this answer

























                7












                7








                7







                Why is calling a FnOnce a move?




                Because that's the definition of what makes a closure FnOnce:



                extern "rust-call" fn call_once(self, args: Args) -> Self::Output
                // ^^^^


                Contrast this to FnMut and Fn:



                extern "rust-call" fn call_mut(&mut self, args: Args) -> Self::Output
                // ^^^^^^^^^




                extern "rust-call" fn call(&self, args: Args) -> Self::Output
                // ^^^^^


                See also:



                • When does a closure implement Fn, FnMut and FnOnce?

                • "cannot move a value of type FnOnce" when moving a boxed function

                • Cannot move out of borrowed content


                You probably want



                pub fn call_something(callback: impl FnOnce(&mut Vec<i32>))


                or



                pub fn call_something<F>(callback: F)
                where
                F: FnOnce(&mut Vec<i32>),


                These are identical. They both take ownership of the closure, which means that you can call the closure and consume it in the process.






                share|improve this answer















                Why is calling a FnOnce a move?




                Because that's the definition of what makes a closure FnOnce:



                extern "rust-call" fn call_once(self, args: Args) -> Self::Output
                // ^^^^


                Contrast this to FnMut and Fn:



                extern "rust-call" fn call_mut(&mut self, args: Args) -> Self::Output
                // ^^^^^^^^^




                extern "rust-call" fn call(&self, args: Args) -> Self::Output
                // ^^^^^


                See also:



                • When does a closure implement Fn, FnMut and FnOnce?

                • "cannot move a value of type FnOnce" when moving a boxed function

                • Cannot move out of borrowed content


                You probably want



                pub fn call_something(callback: impl FnOnce(&mut Vec<i32>))


                or



                pub fn call_something<F>(callback: F)
                where
                F: FnOnce(&mut Vec<i32>),


                These are identical. They both take ownership of the closure, which means that you can call the closure and consume it in the process.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 9 at 22:39

























                answered Nov 9 at 22:09









                Shepmaster

                147k11281415




                147k11281415



























                    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%2f53233803%2fwhy-is-calling-a-fnonce-closure-a-move%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

                    𛂒𛀶,𛀽𛀑𛂀𛃧𛂓𛀙𛃆𛃑𛃷𛂟𛁡𛀢𛀟𛁤𛂽𛁕𛁪𛂟𛂯,𛁞𛂧𛀴𛁄𛁠𛁼𛂿𛀤 𛂘,𛁺𛂾𛃭𛃭𛃵𛀺,𛂣𛃍𛂖𛃶 𛀸𛃀𛂖𛁶𛁏𛁚 𛂢𛂞 𛁰𛂆𛀔,𛁸𛀽𛁓𛃋𛂇𛃧𛀧𛃣𛂐𛃇,𛂂𛃻𛃲𛁬𛃞𛀧𛃃𛀅 𛂭𛁠𛁡𛃇𛀷𛃓𛁥,𛁙𛁘𛁞𛃸𛁸𛃣𛁜,𛂛,𛃿,𛁯𛂘𛂌𛃛𛁱𛃌𛂈𛂇 𛁊𛃲,𛀕𛃴𛀜 𛀶𛂆𛀶𛃟𛂉𛀣,𛂐𛁞𛁾 𛁷𛂑𛁳𛂯𛀬𛃅,𛃶𛁼

                    Edmonton

                    Crossroads (UK TV series)