From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: Simon Marchi <simark@simark.ca>,
gdb-patches@sourceware.org,
Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH v2 1/3] Use a newtype for remote file descriptor
Date: Fri, 27 Feb 2026 11:22:49 -0700 [thread overview]
Message-ID: <87342mujuu.fsf@tromey.com> (raw)
In-Reply-To: <877bryuk4a.fsf@tromey.com> (Tom Tromey's message of "Fri, 27 Feb 2026 11:17:09 -0700")
Simon> With this patch, we now have 2 different classes names scoped_target_fd.
Simon> Is it a problem, ODR-wise? It looks like they have the same goal, so we
Simon> could perhaps merge them.
I looked and they aren't the same, the remote.c one needs the underlying
'int' type.
Tom
next prev parent reply other threads:[~2026-02-27 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 14:28 [PATCH v2 0/3] Stronger typing for remote file i/o Tom Tromey
2026-02-27 14:28 ` [PATCH v2 1/3] Use a newtype for remote file descriptor Tom Tromey
2026-02-27 16:30 ` Simon Marchi
2026-02-27 18:17 ` Tom Tromey
2026-02-27 18:22 ` Tom Tromey [this message]
2026-02-27 14:28 ` [PATCH v2 2/3] Use enum types for remote fileio flags Tom Tromey
2026-02-27 14:28 ` [PATCH v2 3/3] Use bool for "warn_if_slow" Tom Tromey
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87342mujuu.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=simon.marchi@efficios.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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