Skip to content

File an LWG issue about char_traits::eq() being underspecified #2691

Description

See this comment thread: #2676 (comment)

For example, char_traits::eq() should consider the null terminator to be distinct from every other value.

Activity

  1. frederick-vs-ja commented on Apr 30, 2022

    @frederick-vs-ja
    Contributor

    It may be difficult to make such specification when there's no operator== for T, or when equality comparison results in UB for T() (while eq is still well-defined). Not sure whether "value representation" is suitable here.

  2. frederick-vs-ja commented on May 7, 2022

    @frederick-vs-ja
    Contributor

    LWG-3694 is filed now.

  3. StephanTLavavej commented on May 9, 2022

    @StephanTLavavej
    MemberAuthor

    Thank you! 😻

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    LWG issue neededA wording defect that should be submitted to LWG as a new issueresolvedSuccessfully resolved without a commit

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions