Article View: pl.comp.lang.c
Article #309403iteracja po elementach std::tuple
From: Maciek
Date: Sat, 19 Aug 2017 19:53
Date: Sat, 19 Aug 2017 19:53
3 lines
1459 bytes
1459 bytes
Cześć, jak mogę wykorzystać najnowsze (w sensie do c++17 włącznie) standardy aby iterować po elementach std::tuple bez wiedzy o tym ile jest tych elementów ? Dzięki.
Technical Details
Message-ID:
<8119a4ef-1814-4955-acea-00fc766fa5d6@googlegroups.com>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!agh.edu.pl!news.agh.edu.pl!newsfeed2.atman.pl!newsfeed.atman.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!peer02.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!v29no359211qtv.0!news-out.google.com!n39ni15095qtf.1!nntp.google.com!v29no359208qtv.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mailShow Full Headers
Complete Article Headers
X-Received: by 10.31.146.206 with SMTP id u197mr8021256vkd.35.1503172389424; Sat, 19 Aug 2017 12:53:09 -0700 (PDT) X-Received: by 10.31.170.198 with SMTP id t189mr131148vke.13.1503172389350; Sat, 19 Aug 2017 12:53:09 -0700 (PDT) Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!agh.edu.pl!news.agh.edu.pl!newsfeed2.atman.pl!newsfeed.atman.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!peer02.am4!peer.am4.highwinds-media.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!v29no359211qtv.0!news-out.google.com!n39ni15095qtf.1!nntp.google.com!v29no359208qtv.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: pl.comp.lang.c Date: Sat, 19 Aug 2017 12:53:09 -0700 (PDT) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=178.43.79.50; posting-account=SOZBVwoAAAAtP6gAgjkK3BR3YPR_ux-s NNTP-Posting-Host: 178.43.79.50 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <8119a4ef-1814-4955-acea-00fc766fa5d6@googlegroups.com> Subject: iteracja po elementach std::tuple From: Maciek <moblaza@gmail.com> Injection-Date: Sat, 19 Aug 2017 19:53:09 +0000 X-Received-Body-CRC: 461714261 X-Received-Bytes: 1351 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit