Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6102549
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T13:37:36+00:00 2026-05-23T13:37:36+00:00

When constructing a std::string from a const char* , I often use the following

  • 0

When constructing a std::string from a const char*, I often use the following pattern:

const char* p = GetString();
std::string s(p);

I suppose I could use the similar pattern:

const char* p = GetString();
std::string s = p;

But, when I want to assign, rather than construct, to a std::string from a const char*, I have too many choices:

s = p;
s.assign(p);
std::string(p).swap(s);

Are the choices above more-or-less equivalent? Which should I prefer, and why?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T13:37:37+00:00Added an answer on May 23, 2026 at 1:37 pm

    Go for readability, and just use the idiomatic operator= for assignment. Also, directly construct the std::string from the const char*.

    std::string s(GetString());
    s = GetString();
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

std::exception requires that its constructor be throw() . Yet std::runtime_error accepts a std::string as
MWE #include <iostream> struct Foo { Foo() { std::cout << Constructing Foo << this
I'm constructing a simple container class but run into some problems (reassembling the ones
I read through a lot of circular dependency topics but all of them seem
My variables aren't producing data like they should be. For whatever reason, my string
I'm interested in building an uninitialized_vector container, which will be semantically identical to std::vector
Have a homework assignment in which I'm supposed to create a vector of pointers
So I got a class that specifies a constant with a special meaning for
So one rule of thumb I've heard with respect to modern C++ style is

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.