220 18442 <04ad9302-fccd-4567-a09d-85de7a303b10@isocpp.org> article Path: news.gmane.org!not-for-mail From: german.diago@hubblehome.com Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Exposing string small string optimization size to avoid heap allocation. Date: Fri, 5 Jun 2015 23:51:27 -0700 (PDT) Lines: 112 Approved: news@gmane.org Message-ID: <04ad9302-fccd-4567-a09d-85de7a303b10@isocpp.org> References: <19736033-58d4-441d-ae73-19804f8ef575@isocpp.org> <87107DC2-569D-4411-8CCA-548E59529C96@mac.com> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_318_358007323.1433573487217" X-Trace: ger.gmane.org 1433573493 30818 80.91.229.3 (6 Jun 2015 06:51:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 6 Jun 2015 06:51:33 +0000 (UTC) Cc: potswa@mac.com To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDKJVOEEVYNRB4FQZKVQKGQEMTKD5WA@isocpp.org Sat Jun 06 08:51:33 2015 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-yk0-f198.google.com ([209.85.160.198]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Z17x3-0001si-Ux for gclcip-std-proposals@m.gmane.org; Sat, 06 Jun 2015 08:51:30 +0200 Original-Received: by ykfl8 with SMTP id l8sf70193689ykf.0 for ; Fri, 05 Jun 2015 23:51:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:message-id:in-reply-to :references:subject:mime-version:content-type:x-original-sender :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:list-subscribe:list-unsubscribe; bh=ZIgSDUjnQeuCVJ+pgq2hSTGp5ycoQ2mJiE3atCWb9sg=; b=ln0+4DWElU+nyUBry5orP45+fzvSYn+LNf/bUf5IrihU/XwQ5VnfqxJXZ4MAKRMEIL tqLGBByu0oTyhc8QSCITf+XjEbGIwekF7Lm6U4fYOMplqkLWcBvvmiMOtBdconOENhiD Fy3MZXj3bT4N9UPFEu1aisipuwneGbUUZ1CjV3PTCWBbYy6PslADG4zBKqPS6aZj/O0K 30N7VKEQf5G/l8BPoJmUlsoVmDsedMSPcHaG2dOtLJxDP/gMUeCodBKaJb+NuYbs4BIP AVKhF8AoIse1csBqEHzVy0YM7h+dESYQyqq1gk3YDTHDL1t6SyO9kjtUWGedYx/XhawI ZleA== X-Gm-Message-State: ALoCoQkhut7COcKOElKMFdolSGvXMik1+UjMJWvB5sS8i+3zbSP41OoESkNmHleVvrImADeU//um X-Received: by 10.140.236.67 with SMTP id h64mr8893595qhc.13.1433573488871; Fri, 05 Jun 2015 23:51:28 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.50.102.3 with SMTP id fk3ls762194igb.34.gmail; Fri, 05 Jun 2015 23:51:28 -0700 (PDT) X-Received: by 10.50.66.141 with SMTP id f13mr30033igt.4.1433573488010; Fri, 05 Jun 2015 23:51:28 -0700 (PDT) In-Reply-To: <87107DC2-569D-4411-8CCA-548E59529C96@mac.com> X-Original-Sender: german.diago@hubblehome.com Precedence: list Mailing-list: list std-proposals@isocpp.org; contact std-proposals+owners@isocpp.org List-ID: X-Google-Group-Id: 399137483710 List-Post: , List-Help: , List-Archive: List-Subscribe: , List-Unsubscribe: , Xref: news.gmane.org gmane.comp.lang.c++.isocpp.proposals:18442 Archived-At: ------=_Part_318_358007323.1433573487217 Content-Type: multipart/alternative; boundary="----=_Part_319_1927382414.1433573487217" ------=_Part_319_1927382414.1433573487217 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Saturday, June 6, 2015 at 12:36:39 PM UTC+7, David Krauss wrote: > > > On 2015=E2=80=9306=E2=80=9306, at 1:14 PM, german...@hubblehome.com wrote: > > Any interest in this? > > > If heap allocation is really unimplemented, it=E2=80=99s already called= =20 > string::max_size(). And it wouldn=E2=80=99t really be considered an optim= ization=20 > since there=E2=80=99s no alternative. > > I think this is just an implementation-defined constant. Not sure wether = I=20 am wrong or not. Is that a lot of work? =20 > Otherwise, I=E2=80=99m not sure what a program would do with it. Chopping= the ends=20 > off string literals that don=E2=80=99t need to be self-explanatory? Seems= like a=20 > lot of trouble for little gain. > A common use case is to have a lot of short strings. I want to store them= =20 in std::string (maybe) to have some convenience of the operations it=20 provides. If I do not know wether the string will allocate memory, how can= =20 I use std::strings in the first place? But maybe (and maybe only, I am not sure) a std::static_string is a=20 better interface for this.=20 Thanks for your feedback. =20 --=20 ---=20 You received this message because you are subscribed to the Google Groups "= ISO C++ Standard - Future Proposals" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposals+unsubscribe@isocpp.org. To post to this group, send email to std-proposals@isocpp.org. Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposa= ls/. ------=_Part_319_1927382414.1433573487217 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Saturday, June 6, 2015 at 12:36:39 PM UTC+7, Da= vid Krauss wrote:

On 2015=E2= =80=9306=E2=80=9306, at 1:14 PM, german...@hubblehome.com wrote:

Any interest in this?

If heap allocation is really unimplemented, it=E2=80=99s already called string::max_size(). And it wouldn=E2=80=99t rea= lly be considered an optimization since there=E2=80=99s no alternative.

I think this is just an implementa= tion-defined constant. Not sure wether I am wrong or not. Is that a lot of = work?
 
Otherwise, I=E2=80=99m no= t sure what a program would do with it. Chopping the ends off string litera= ls that don=E2=80=99t need to be self-explanatory? Seems like a lot of trou= ble for little gain.

A common u= se case is to have a lot of short strings. I want to store them in std::str= ing (maybe) to have some convenience of the operations it provides. If I do= not know wether the string will allocate memory, how can I use std::string= s in the first place?

But maybe (and maybe only, I= am not sure) a std::static_string<N> is a better interface for this.=  

Thanks for your feedback.
 <= br>

--

---
You received this message because you are subscribed to the Google Groups &= quot;ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to std-proposa= ls+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
Visit this group at http://groups.google.com/a/isocpp.org/group/std-proposals/<= /a>.
------=_Part_319_1927382414.1433573487217-- ------=_Part_318_358007323.1433573487217-- .