Скачать или смотреть How to Prohibit Overriding Returned References in C+ + 17

Learn how to prevent the overriding of returned references in C+ + 17 and simplify your functions effectively.
---
This video is based on the question https://stackoverflow.com/q/66006344/ asked by the user 'NexCastus' ( https://stackoverflow.com/u/9451034/ ) and on the answer https://stackoverflow.com/a/66006498/ provided by the user 'user2807083' ( https://stackoverflow.com/u/2807083/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: prohibit that the returned reference of a function is overridden by a assignment

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How to Prohibit Overriding Returned References in C+ + 17

In C+ + programming, there's a common scenario where you might want to return a reference from a function. However, this can lead to unintended consequences if the returned reference is accidentally overridden by an assignment statement. This article discusses how to avoid such issues in C+ + 17, which can enhance the reliability and readability of your code.

The Issue at Hand

Let's consider the following code snippet that demonstrates the problem:

[[See Video to Reveal this Text or Code Snippet]]

In this example, using Error.doSomething(0) on the left side of an assignment can lead to confusion and potential bugs. The aim here is to prohibit this kind of behavior, ensuring that the returned reference cannot be assigned to another object like b.

Why Prohibiting Reference Assignment is Essential

When you return a reference, it expects users to treat it as a valid and immutable reference. Allowing it to be on the left-hand side of an assignment can lead to:

Accidental Data Overwrites: The original data may be unintentionally modified.

Code Misunderstanding: Other programmers reading the code may not realize that they are dealing with a function reference, leading to unexpected behaviors.

To avoid these pitfalls in C+ + 17, you can choose one of the following solutions:

Solution 1: Return by Value

One of the simplest approaches is to return the object by value. This way, the returned object cannot be used as the assignment target:

[[See Video to Reveal this Text or Code Snippet]]

Advantages of Returning by Value

Simplicity: It’s easy to understand for anyone reading your code.

Safety: The return value cannot be assigned anything else, preserving its integrity.

Solution 2: Return a Constant Reference

An alternative is to return a constant reference from the function. This will allow users to read the value but prevent them from modifying it:

[[See Video to Reveal this Text or Code Snippet]]

Benefits of Returning a Constant Reference

Efficiency: It avoids unnecessary copying of objects that can be expensive in terms of performance.

Prevent Modification: By using const, you ensure that no assignment can happen.

Conclusion

By implementing one of the above solutions in your C+ + 17 code, you can prohibit overriding returned references, thereby improving the safety and reliability of your applications. Whether you choose to return by value or by constant reference ultimately depends on your specific needs, but both methods ensure that the returned object maintains its integrity and prevents unintentional modifications.

By incorporating these practices, you can streamline your coding process, making your code cleaner and easier to manage.