To know about what is move semantics?

Question

1.00/5 (1 vote)

See more:

Hi, actually am trying to understand about the move semantics the thing is am not getting the theory in practically. Only one doubt is how move semantics moves bcz in move constructor am using move function, the theory says that transfer the ownership to another resource means copy constructor will call right. I don't know how move Constructor working anyway it needs to copy right. So, help me how move semantics works and information of address of object after the move constructor pls describe in-depth.

What I have tried:

Tried to understand about the move semantics nut having some doubts.

Posted 14-Dec-23 5:48am

Mathi Prasad

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

steveb · Answer 1 · 2023-12-14T10:01:00

In order to understand the move semantics, first and foremost you must understand what a temporary object is. Which is, any object created on the fly and then is immideately discarded:

C++

class A{/*assume it has functionality*/};

A a; // Solid object
A a1 = A(/* constructor parameter(s)*/); // Where as a1 is solid, the RValue assignment is a temporary objest which is when discarded triggers destructor semanticts

So move semantics says Move A() into a1, no copying like having 2 object temprarily occupying memory.

That can work even without the move semantics, given that proper copy constructor and assignmens are implemented. But the move semantics eliminates redundant copies, say if the object is huge in size.

Bruno van Dooren · Answer 2 · 2023-12-14T22:33:00

I cover move semantics in one of my articles

[^]

Move semantics basically 'move' the internal state of an object into another object in the right circumstances, thereby avoiding the need for creating a new object and copying its state.

It is the compiler which will determine this during compilation. It looks at your assignment and based on whether it deems certain variable to be 'temporary', it can 'move' the internal state of the temporary variable into your target value without having to go through a copy constructor.

Note however that this is not always safe. Implemented wrongly, this can lead to memory leaks if the target object does not properly discard its internal resources before they are overwritten.

To know about what is move semantics?

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0