Skip to content

Fix issue-268: change return type from non-const to const#324

Merged
StephanTLavavej merged 1 commit intomicrosoft:masterfrom
lozinska:issue-268
Dec 5, 2019
Merged

Fix issue-268: change return type from non-const to const#324
StephanTLavavej merged 1 commit intomicrosoft:masterfrom
lozinska:issue-268

Conversation

@lozinska
Copy link
Copy Markdown
Contributor

@lozinska lozinska commented Nov 21, 2019

Description

Update return type of locale& to const locale&

Fixes #268.

Checklist

Be sure you've read README.md and understand the scope of this repo.

If you're unsure about a box, leave it unchecked. A maintainer will help you.

  • Identifiers in product code changes are properly _Ugly as per
    https://eel.is/c++draft/lex.name#3.1 or there are no product code changes.
  • The STL builds successfully and all tests have passed (must be manually
    verified by an STL maintainer before automated testing is enabled on GitHub,
    leave this unchecked for initial submission).
  • These changes introduce no known ABI breaks (adding members, renaming
    members, adding virtual functions, changing whether a type is an aggregate
    or trivially copyable, etc.).
  • These changes were written from scratch using only this repository,
    the C++ Working Draft (including any cited standards), other WG21 papers
    (excluding reference implementations outside of proposed standard wording),
    and LWG issues as reference material. If they were derived from a project
    that's already listed in NOTICE.txt, that's fine, but please mention it.
    If they were derived from any other project (including Boost and libc++,
    which are not yet listed in NOTICE.txt), you must mention it here,
    so we can determine whether the license is compatible and what else needs
    to be done.

@lozinska lozinska requested a review from a team as a code owner November 21, 2019 18:05
Copy link
Copy Markdown
Member

@StephanTLavavej StephanTLavavej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! This changes our implementation to do what the Standard says, and I've verified with Wandbox and Compiler Explorer that libstdc++ and libc++ behave identically. There's a very low risk of source breakage from this change - assignment expressions are sometimes used in chained assignments (where this would continue to work) and occasionally used in other expressions, but typically not in modifying ways. I believe we should go ahead and merge this; we can always go back to the old signature if and when an LWG issue is filed and resolved.

Copy link
Copy Markdown
Member

@BillyONeal BillyONeal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution!

@StephanTLavavej
Copy link
Copy Markdown
Member

I'm porting this to our Microsoft-internal repo in order to run a full build and test pass.

@StephanTLavavej StephanTLavavej merged commit 20adb42 into microsoft:master Dec 5, 2019
@StephanTLavavej
Copy link
Copy Markdown
Member

Everything passed, thanks again for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

<locale>: locale's copy assignment has incorrect return type

3 participants