Comments on: “auto to stick” and Changing Your Style

By: Jonathan Boccara

Jonathan Boccara — Fri, 16 Nov 2018 13:24:00 +0000

In reply to Florian Schmidt. Yes! Well spotted Florian, this is now fixed. Thanks!

By: Florian Schmidt

Florian Schmidt — Thu, 15 Nov 2018 14:38:00 +0000

Thanks for this informative post, I have a question on

auto X = x(); // no way to interpret this as a function declaration

Is it possible you switched type X and variable name x, or did I miss something?

By: Jonathan Boccara

Jonathan Boccara — Thu, 08 Nov 2018 11:54:00 +0000

In reply to Mateus Furquim. Yes it is using braces initialization, here is an example that compiles.

By: Mateus Furquim

Mateus Furquim — Thu, 01 Nov 2018 00:34:00 +0000

s this line of code in the post correct?
`auto name = std::string{“Arthur”};`
It is using `{` instead of `(`.

By: Akim Demaille

Akim Demaille — Sat, 27 Oct 2018 12:50:00 +0000

I’m using auto almost always. And I also use const almost always: I love to see when “variables” are actually just constants. The compiler knows by reading the code, but the newcomers arriving to a piece of code have an immediate benefit to see that a variable is actually just a convenient name for a value rather than a location in memory.

So my wildest dream in C++ would be to no longer write auto, but _only_ const.

“`
const myWidget = Widget{42};
const end = vector.end();

const client = [&]
{
auto peers = Peers{};
peers.emplace_back(std::make_unique(11));
peers.emplace_back(std::make_unique(12, servers[1]));
peers.emplace_back(std::make_unique(13, servers[2]));
return paxos::Client(3, std::move(peers));
}();“`

etc.

By: Oleksandr Prokopenko

Oleksandr Prokopenko — Thu, 11 Oct 2018 10:14:00 +0000

float x = 42;
is more self-documentary. And using this argument, in five years your colleague will refactor the same line of code by replacing auto with generic Number:
Number x = 42.f;
float->auto->Number… I am wondering you have enough time to keep your code base up with this ‘marketing’ of auto.

By: Aymen Schehaider

Aymen Schehaider — Tue, 02 Oct 2018 09:50:00 +0000

Yeah Ready to adopt “auto to stick” at work.

By: Paul Cook

Paul Cook — Tue, 02 Oct 2018 05:31:00 +0000

In reply to Furkan Üzümcü.

I thought that. The user would have accidentally written

auto x – 42.;

and accidentally declared a double instead of a float, which would cause all sorts of potential confusion.

By: Paul Cook

Paul Cook — Tue, 02 Oct 2018 05:28:00 +0000

In reply to Rud Merriam.

Simple answer – scope overloading:

Your proposed syntax:

x = 20;

void f()
{
x = 10; // do I mean to change outer x or declare a new variable?
}

By: Shafik Yaghmour

Shafik Yaghmour — Mon, 01 Oct 2018 23:18:00 +0000

Note

float x = 42.;

Is not a narrowing conversion because it is a constant expression that after conversion can fit into the range of the destination after conversion. See [dcl.init.list]p7.2 http://eel.is/c++draft/dcl.init.list#7.2