public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
To: Simon Marchi via Gdb-patches <>
Cc: Simon Marchi <>
Subject: Re: [PATCH 1/2] gdbsupport: allow passing nullptr to checked_static_cast
Date: Tue, 31 Jan 2023 10:35:19 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Simon Marchi via Gdb-patches's message of "Tue, 31 Jan 2023 10:57:20 -0500")

>>>>> "Simon" == Simon Marchi via Gdb-patches <> writes:

Simon> Both static_cast and dynamic_cast handle nullptr (they return nullptr),
Simon> so I think checked_static_cast should too.  This will allow doing a null
Simon> check after a checked_static_cast:

Thanks, I think this is a good idea.


      parent reply	other threads:[~2023-01-31 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31 15:57 Simon Marchi
2023-01-31 15:57 ` [PATCH 2/2] gdb: add nullptr check to cooked_index_functions::dump Simon Marchi
2023-01-31 17:35   ` Tom Tromey
2023-01-31 18:22     ` Simon Marchi
2023-01-31 17:35 ` Tom Tromey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).