News for hackers. Stuff that matters.
Re:Short intro to C++ for Rust developers: Ownership and Bor... by criddell on Sunday January 22, 2017 @09:41PM (#13459291)
I have a C++ question. In the article, the author writes the Person constructor this way:

  Person(std::string first_name, std::string last_name)
    : first_name(std::move(first_name))
    , last_name(std::move(last_name))
  {}
For string parameters, do you need to use std::move()? Won't the compiler do that anyway?

And does anybody really put the comma separating initializers at the start of the line? Yuck.

Re:Short intro to C++ for Rust developers: Ownership and Bor... by tomjakubowski on Sunday January 22, 2017 @10:19PM (#13459475)
> And does anybody really put the comma separating initializers at the start of the line? Yuck.

I don't, but I can see why someone would. When you copy-paste initializer lines around (say, because you've re-ordered members in the declaration), a leftover trailing comma often leads to insanely painful compiler errors. Organizing the commas this way makes that less likely.

Re:Short intro to C++ for Rust developers: Ownership and Bor... by kchoudhu on Sunday January 22, 2017 @10:03PM (#13459388)
I do. Easier to comment things out when necessary.

Hangover from SQL as well.

Re:Short intro to C++ for Rust developers: Ownership and Bor... by flukus on Sunday January 22, 2017 @10:26PM (#13459523)
I wish trailing commas were more widely supported in programming languages.
Re:Short intro to C++ for Rust developers: Ownership and Bor... by GrayShade on Monday January 23, 2017 @06:14AM (#13461362)
It's the same. You can comment out the last line easier, but not the first one. With trailing commas, it's the other way around.
Re:Short intro to C++ for Rust developers: Ownership and Bor... by masklinn on Monday January 23, 2017 @08:44AM (#13462084)
> With trailing commas, it's the other way around.

If the language supports trailing commas[0] (rather than just interspersed ones) that's not an issue as you could write:

    Person(std::string first_name, std::string last_name):
        first_name(std::move(first_name)),
        last_name(std::move(last_name)),
    {}
[0] as Python, Ruby, Javascript or Rust do
Re:Short intro to C++ for Rust developers: Ownership and Bor... by Noughmad on Monday January 23, 2017 @03:10AM (#13460654)
No, you should almost never use std::move. Instead, the parameters should be "const std::string&". This way, you avoid all the unnecessary copies and moves.
Re:Short intro to C++ for Rust developers: Ownership and Bor... by silent_hunter on Monday January 23, 2017 @07:16AM (#13461626)
"const string&" - will always make a copy of the string for first_name and last_name, if we write "Person(std::string first_name, std::string last_name) : first_name(first_name) , last_name(last_name) {}" in case passed arguments are lvalues they will be copied, otherwise moved.