From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH 1/3] do full type check in COPY_ARRAY and MOVE_ARRAY
Date: Sun, 01 Jan 2023 12:59:43 +0900 [thread overview]
Message-ID: <xmqqsfguhplc.fsf@gitster.g> (raw)
In-Reply-To: <xmqq8rinhs7t.fsf@gitster.g> (Junio C. Hamano's message of "Sun, 01 Jan 2023 12:03:02 +0900")
Junio C Hamano <gitster@pobox.com> writes:
> ... I think what you ideally want to enforce is that
> typeof(dst) is exactly typeof(src), or typeof(src) sans constness
> (i.e. you can populate non-const array from a const template)?
IOW, I am wondering if something like this is an improvement.
git-compat-util.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git c/git-compat-util.h w/git-compat-util.h
index a76d0526f7..be435615f0 100644
--- c/git-compat-util.h
+++ w/git-compat-util.h
@@ -97,8 +97,13 @@ struct strbuf;
# define BARF_UNLESS_AN_ARRAY(arr) \
BUILD_ASSERT_OR_ZERO(!__builtin_types_compatible_p(__typeof__(arr), \
__typeof__(&(arr)[0])))
+# define ARRAYS_COPYABLE_OR_ZERO(src,dst) \
+ (BUILD_ASSERT_OR_ZERO(!__builtin_types_compatible_p(__typeof__(src), \
+ __typeof__(dst))) + \
+ (0 ? *(dst) = *(src) : 0))
#else
# define BARF_UNLESS_AN_ARRAY(arr) 0
+# define ARRAYS_COPYABLE_OR_ZERO(src,dst) (0 ? *(dst) = *(src) : 0))
#endif
/*
* ARRAY_SIZE - get the number of elements in a visible array
next prev parent reply other threads:[~2023-01-01 3:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 21:51 [PATCH 0/3] COPY_ARRAY, MOVE_ARRAY, DUP_ARRAY René Scharfe
2022-12-30 21:56 ` [PATCH 1/3] do full type check in COPY_ARRAY and MOVE_ARRAY René Scharfe
2023-01-01 3:03 ` Junio C Hamano
2023-01-01 3:59 ` Junio C Hamano [this message]
2023-01-01 7:41 ` René Scharfe
2023-01-01 10:45 ` René Scharfe
2023-01-01 12:11 ` Junio C Hamano
2023-01-01 12:32 ` René Scharfe
2023-01-01 12:46 ` Junio C Hamano
2022-12-30 22:02 ` [PATCH 2/3] add DUP_ARRAY René Scharfe
2022-12-30 22:03 ` [PATCH 3/3] use DUP_ARRAY René Scharfe
2023-01-01 21:05 ` [PATCH v2 0/4] COPY_ARRAY, MOVE_ARRAY, DUP_ARRAY René Scharfe
2023-01-01 21:08 ` [PATCH v2 1/4] factor out BARF_UNLESS_COPYABLE René Scharfe
2023-01-01 21:11 ` [PATCH v2 2/4] do full type check in BARF_UNLESS_COPYABLE René Scharfe
2023-01-08 7:28 ` Junio C Hamano
2023-01-08 10:10 ` René Scharfe
2023-01-09 4:27 ` Junio C Hamano
2023-01-09 18:08 ` Jeff Hostetler
2023-01-01 21:14 ` [PATCH v2 3/4] add DUP_ARRAY René Scharfe
2023-01-01 21:16 ` [PATCH v2 4/4] use DUP_ARRAY René Scharfe
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=xmqqsfguhplc.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
/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;
as well as URLs for NNTP newsgroup(s).