To get a trial key
fill out the form below
Team License (a basic version)
Enterprise License (an extended version)
* By clicking this button you agree to our Privacy Policy statement

Request our prices
New License
License Renewal
--Select currency--
USD
EUR
GBP
RUB
* By clicking this button you agree to our Privacy Policy statement

Free PVS-Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
>
Expressions: value categories and refer…

Expressions: value categories and reference types

Sep 17 2021

Each expression in C++ has two properties – a type and a value category. Depending on the value category, a reference of a certain kind may be bound to an expression.

Value categories

Before move semantics, there were two categories of expressions in C++ – lvalue and rvalue. To differentiate between lvalue and rvalue, the following rule was used: if an expression could appear on the left-hand side of an assignment expression, then it is lvalue. Otherwise, it is rvalue.

The C++11 standard introduced new value categories to support move semantics – glvalue, prvalue, and xvalue. Now any expression can belong to one of these categories.

An rvalue is a union of prvalue and xvalue. An glvalue is a union of lvalue and xvalue.

The C++ standard does not give an official definition of categories. The paper specifies which value category each expression type has.

To differentiate between lvalue, xvalue and prvalue, you can use the following rule:

  • An expression is a prvalue if it is a temporary unnamed object. For example, i++.
  • An expression is an xvalue if it is a named object whose resources can be reused. An expression is also an xvalue if it is the result of the static_cast<type &&> expression or the result of calling a function that returns type &&. For example, std::move (obj).
  • All other expressions are lvalue. For example, *ptr.

Reference kinds

Before C++11, there was only one reference kind. If you wanted to take a reference to the var variable of the type type, you had to write the following:

type &ref = var;

Such a reference is called an lvalue reference. It can be bound only to an lvalue expression.

To support move semantics, new reference types became available – an rvalue reference and a forwarding reference. If an rvalue reference is required, you must write the following:

type &&ref = rvalue_expr;

Such reference, unlike an lvalue reference, must refer to an rvalue expression.

A forwarding reference is now available:

template <typename T>
void foo(T &&arg);

where T is the template parameter derived from the function template argument. Such declaration looks like an rvalue reference declaration, but it functions differently. Due to reference collapsing, a forwarding reference can be bound to lvalue and rvalue objects. Here is the detailed description of this mechanism.

Do not confuse forwarding and rvalue references. In the example below, the T template parameter corresponds to the Base class, not to the foo function. Therefore, the arg argument of the foo function is an rvalue reference, not a forwarding one:

template <typename T>
class Base
{
  void foo(T&& arg);
};

A forwarding reference allows implementing perfect forwarding. This mechanism is responsible for moving an object of a certain type as expected: an rvalue object is moved, an lvalue object is copied. The std::forward function is the implementation of perfect forwarding in the standard library.

Popular related articles
Characteristics of PVS-Studio Analyzer by the Example of EFL Core Libraries, 10-15% of False Positives

Date: Jul 31 2017

Author: Andrey Karpov

After I wrote quite a big article about the analysis of the Tizen OS code, I received a large number of questions concerning the percentage of false positives and the density of errors (how many erro…
Free PVS-Studio for those who develops open source projects

Date: Dec 22 2018

Author: Andrey Karpov

On the New 2019 year's eve, a PVS-Studio team decided to make a nice gift for all contributors of open-source projects hosted on GitHub, GitLab or Bitbucket. They are given free usage of PVS-Studio s…
The Evil within the Comparison Functions

Date: May 19 2017

Author: Andrey Karpov

Perhaps, readers remember my article titled "Last line effect". It describes a pattern I've once noticed: in most cases programmers make an error in the last line of similar text blocks. Now I want t…
The Last Line Effect

Date: May 31 2014

Author: Andrey Karpov

I have studied many errors caused by the use of the Copy-Paste method, and can assure you that programmers most often tend to make mistakes in the last fragment of a homogeneous code block. I have ne…
The way static analyzers fight against false positives, and why they do it

Date: Mar 20 2017

Author: Andrey Karpov

In my previous article I wrote that I don't like the approach of evaluating the efficiency of static analyzers with the help of synthetic tests. In that article, I give the example of a code fragment…
Appreciate Static Code Analysis!

Date: Oct 16 2017

Author: Andrey Karpov

I am really astonished by the capabilities of static code analysis even though I am one of the developers of PVS-Studio analyzer myself. The tool surprised me the other day as it turned out to be sma…
How PVS-Studio Proved to Be More Attentive Than Three and a Half Programmers

Date: Oct 22 2018

Author: Andrey Karpov

Just like other static analyzers, PVS-Studio often produces false positives. What you are about to read is a short story where I'll tell you how PVS-Studio proved, just one more time, to be more atte…
PVS-Studio for Java

Date: Jan 17 2019

Author: Andrey Karpov

In the seventh version of the PVS-Studio static analyzer, we added support of the Java language. It's time for a brief story of how we've started making support of the Java language, how far we've co…
Technologies used in the PVS-Studio code analyzer for finding bugs and potential vulnerabilities

Date: Nov 21 2018

Author: Andrey Karpov

A brief description of technologies used in the PVS-Studio tool, which let us effectively detect a large number of error patterns and potential vulnerabilities. The article describes the implementati…
Static analysis as part of the development process in Unreal Engine

Date: Jun 27 2017

Author: Andrey Karpov

Unreal Engine continues to develop as new code is added and previously written code is changed. What is the inevitable consequence of ongoing development in a project? The emergence of new bugs in th…

Comments (0)

Next comments
This website uses cookies and other technology to provide you a more personalized experience. By continuing the view of our web-pages you accept the terms of using these files. If you don't want your personal data to be processed, please, leave this site.
Learn More →
Accept