Skip to content

CWG2689 [basic.fundamental] No mention of cv std::nullptr_t in basic.fundamental #223

Description

@anooprana986

Full name of submitter (unless configured in github; will be published with the issue): Anoop Rana

Reference (section label): [basic.fundamental]

Link to reflector thread (if any): #193 (comment)

Issue description: There is no mention of cv qualified std::nullptr_t in basic.fundamental.

Suggested resolution:

Add wording for cv qualified version of std::nullptr_t in [basic.fundamental].

Activity

  1. changed the title [-][basic.fundamental] No mention of cv std::nullptr_t in basic.fundamental[/-] [+]CWG2689 [basic.fundamental] No mention of cv std::nullptr_t in basic.fundamental[/+] on Jan 17, 2023
  2. jensmaurer commented on Jan 17, 2023

    @jensmaurer
    Member
  3. languagelawyer commented on Aug 21, 2023

    @languagelawyer

    Isn't

    The types denoted by std::nullptr_t, const std::nullptr_t, volatile std::nullptr_t, and const volatile std::nullptr_t are distinct types.

    an extremely long and boring way to say

    the type of nullptr is a non-class, non-array object type

    ?

  4. languagelawyer commented on Aug 21, 2023

    @languagelawyer

    How about

    [lex.nullptr]/1

    The pointer literal is the keyword nullptr. It has a distinct fundamental type ([basic.fundamental]) std​::​nullptr_t.

    [basic.fundamental]/16

    The type of nullptr prvalue (and any its cv-qualified version) is a non-class, non-array object type, distinct from other types in this subclause. A value of type std​::​nullptr_t is a null pointer constant ([conv.ptr])…

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions