public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cooky.ykooc922 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107761] Implement C++23 <mdspan>
Date: Tue, 26 Dec 2023 13:39:07 +0000	[thread overview]
Message-ID: <bug-107761-4-yCmP0rneAG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107761-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107761

--- Comment #7 from Desmond Gold <cooky.ykooc922 at gmail dot com> ---
Here's an updated version of the implementation with following changes:
+ followed coding style of GNU (maybe not all)
+ added initial implementation of std::submdspan facilities (without
constraints and preconditions yet)
+ tweaked some of the problems in previous implementation

https://godbolt.org/z/Mxs1YP8n7

summary
+ implemented c++23 <mdspan>
+ implemented c++26 std::submdspan facilities in <mdspan>
  + added c++23 feature (concepts only): '__tuple_like' and '__pair_like'
    to be used by '__mdspan::__index_pair_like'
  + added alias template '_Nth_type_t' which would supposedly be placed
    inside <bits/utility.h>
+ still no documentations, incomplete preconditions and constraints, and
incomplete tests

      parent reply	other threads:[~2023-12-26 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-19 11:33 [Bug libstdc++/107761] New: " redi at gcc dot gnu.org
2022-12-08 20:25 ` [Bug libstdc++/107761] " pinskia at gcc dot gnu.org
2023-08-20 20:40 ` gonzalo.gadeschi at gmail dot com
2023-12-23 14:31 ` cooky.ykooc922 at gmail dot com
2023-12-23 14:46 ` redi at gcc dot gnu.org
2023-12-23 22:44 ` cooky.ykooc922 at gmail dot com
2023-12-24 14:34 ` redi at gcc dot gnu.org
2023-12-26 13:39 ` cooky.ykooc922 at gmail dot com [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:
  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=bug-107761-4-yCmP0rneAG@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).