public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Jeremy Kerr <jk@codeconstruct.com.au>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	linux-man@vger.kernel.org
Subject: Re: [PATCH v2] mctp.7: Add man page for Linux MCTP support
Date: Fri, 12 Nov 2021 21:07:54 +0100	[thread overview]
Message-ID: <8c840e69-e437-2ec8-a8e8-c990f35dffe6@gmail.com> (raw)
In-Reply-To: <02a98db8-6dec-d66b-4cde-81bed9de6620@gmail.com>



On 11/12/21 21:07, Alejandro Colomar (man-pages) wrote:
> 
> 
> On 11/12/21 20:40, G. Branden Robinson wrote:
>> At 2021-11-12T19:45:16+0100, Alejandro Colomar (man-pages) wrote:
>>> Also, we prevent some crazy programmers from relying on that padding
>>> byte being actually padding and not something else, even if it "must"
>>> be zero.  I've seen too much crazy stuff; programmers relying on
>>> undefined behavior just because "we don't plan to move from C++17 to
>>> C++20, so this is safe".
> 
> A more complete report of the horrifying story can be found here:
> <https://github.com/tcbrindle/span/issues/42#event-5473150481>
> 
> The code to which it refers is closed-source, so I can't link to it.
> But you can feel how wrong it was.
> It made use of a library that provided C20's std::span for older 
> standards, and has some specified behavior for what C20 regarded as UB. 
>   Guess what.

D'oh! C++20
-- 
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2021-11-12 20:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11  1:53 [PATCH v2] mctp.7: Add man page for Linux MCTP support Jeremy Kerr
2021-11-11 21:38 ` Alejandro Colomar (man-pages)
2021-11-12  1:12   ` Jeremy Kerr
2021-11-12 18:45     ` Alejandro Colomar (man-pages)
2021-11-12 19:40       ` G. Branden Robinson
2021-11-12 20:07         ` Alejandro Colomar (man-pages)
2021-11-12 20:07           ` Alejandro Colomar (man-pages) [this message]
2021-11-18  5:08       ` Jeremy Kerr
2021-11-22 16:35         ` Alejandro Colomar (man-pages)
2021-11-12  9:35   ` G. Branden Robinson
2021-11-12 19:50     ` Alejandro Colomar (man-pages)
2021-11-22  9:06       ` Bold and italics, semantics and constness (was: [PATCH v2] mctp.7: Add man page for Linux MCTP support) G. Branden Robinson
2021-11-22 11:50         ` Alejandro Colomar (man-pages)
2021-11-22 13:52           ` G. Branden Robinson
2021-11-22 16:00             ` Alejandro Colomar (man-pages)

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=8c840e69-e437-2ec8-a8e8-c990f35dffe6@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=jk@codeconstruct.com.au \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.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