public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bigotp at acm dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/59529] New: fix experimental/string_view end-of-string edge cases Date: Mon, 16 Dec 2013 19:31:00 -0000 [thread overview] Message-ID: <bug-59529-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59529 Bug ID: 59529 Summary: fix experimental/string_view end-of-string edge cases Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: bigotp at acm dot org Created attachment 31448 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31448&action=edit Patch and test update Per http://isocpp.org/files/papers/N3762.html#string.view.ops, for a given string_view sv: stringview sv{"text"}; auto rv = sv.substr(sv.size()); rv should be a string view starting at sv.end() with size zero. In the current implementation this code improperly raises std::out_of_range. Related to this, basic_string_view constructors with length zero and a valid str should not be re-mapped to the internal empty string.
next reply other threads:[~2013-12-16 19:31 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-12-16 19:31 bigotp at acm dot org [this message] 2014-01-24 20:15 ` [Bug libstdc++/59529] " emsr at gcc dot gnu.org 2014-01-27 10:22 ` paolo.carlini at oracle dot com
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-59529-4@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: linkBe 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).