220 13424 article Path: news.gmane.org!not-for-mail From: Matthew Fioravante Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Proposal: Strongly Typed Bitset Date: Wed, 1 Oct 2014 06:42:18 -0700 (PDT) Lines: 65 Approved: news@gmane.org Message-ID: References: <113390b2-9c74-47e2-a943-5d27dd48bdf1@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5618_1454122010.1412170938686" X-Trace: ger.gmane.org 1412170952 32070 80.91.229.3 (1 Oct 2014 13:42:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 1 Oct 2014 13:42:32 +0000 (UTC) Cc: ricky.65@hotmail.com To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDELF54RTIGRBPEJWCQQKGQE2FGFKGI@isocpp.org Wed Oct 01 15:42:24 2014 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-pa0-f72.google.com ([209.85.220.72]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XZKAg-0002ze-Kq for gclcip-std-proposals@m.gmane.org; Wed, 01 Oct 2014 15:42:23 +0200 Original-Received: by mail-pa0-f72.google.com with SMTP id kx10sf5331157pab.3 for ; Wed, 01 Oct 2014 06:42:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe:content-type; bh=27ecayFtn7Ak6bp/AiUNpF2fUp0b1ygQtz6gTQuJ9yE=; b=ccuH+MpIwZcailX8q/QIKm5BLCRhyBrsQo5ozEm845pYZksFo5r6FnJy/6DZV9Qtj2 5ye8BawJ+rK4fgZLrJW/bNqiZXJzcINPZ2HjFu2ceSOn5H+HaHZeer1wP20F3fBc4nPB x/iIvS7WnQMTZyO7aUuXNfNwlsD0HNtS0bomcYO9LmVbowUly9ANGxLMMR5mf50d2rnD 9daiEebtarC15WYBt5U3pXZS8fujvmT+Ho6xWUFcMIlEjKKKnPjSdRDCecCQB94MOdEF 5Tjv2AZDnLW8UBxJnyf9y/ppqNXn4EYEPLV/CEtlJ2iHMyCTY9UTcrU74XFEoKUGf6Tn r+Bg== 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:x-original-sender:reply-to :precedence:mailing-list:list-id:list-post:list-help:list-archive :list-subscribe:list-unsubscribe:content-type; bh=27ecayFtn7Ak6bp/AiUNpF2fUp0b1ygQtz6gTQuJ9yE=; b=K/4zCp2GzeU3OnCVfKhH6dP1po9JTYIe2gxUVjGRRVTTYwjGvLcbG53l2W/QAhDECz ZDFdFIFI0TVEEpi71yrYxhQ38QFmxc1fnF09EMZcLPTDMl0SZ63HXD5h4zfFqfFbrHu3 vQI9g8MEnMMVIr4S2QnUPQVBVXE7yx6m+6Ucj2/OiwdtRGRAkctCQcc/J7WKvhGd1uOf 9LxtN6xDyl46LyZUR14muSseeX318Bvq0c8Wd4BQtHsiSDyXbIHWjvEZPoJH4DipE+xa jyLwRJiq28mhrQWxUFpArVuSIqJ+Kf3cr00JetdSMwwom9GVfvMeLu23SjRFgL0n1SiJ EcDQ== X-Gm-Message-State: ALoCoQl50r7+nukGoWPUhtagi7/DfS0G7yP1FOCatxlcvprcth88vLXdg/mqtHGW6d6NKa0HUnsD X-Received: by 10.66.222.100 with SMTP id ql4mr47187317pac.32.1412170940831; Wed, 01 Oct 2014 06:42:20 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.140.86.163 with SMTP id p32ls395477qgd.44.gmail; Wed, 01 Oct 2014 06:42:20 -0700 (PDT) X-Received: by 10.140.31.195 with SMTP id f61mr470qgf.41.1412170940032; Wed, 01 Oct 2014 06:42:20 -0700 (PDT) In-Reply-To: <113390b2-9c74-47e2-a943-5d27dd48bdf1@isocpp.org> X-Original-Sender: fmatthew5876@gmail.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:13424 Archived-At: ------=_Part_5618_1454122010.1412170938686 Content-Type: text/plain; charset=UTF-8 On Wednesday, October 1, 2014 9:17:36 AM UTC-4, rick...@hotmail.com wrote: > > > However, I am dubious about the implementator guide of optimizing for > speed over size. In contrast, some may prefer to optimize for size over > speed. > It's a suggestion, not a mandate. On embedded or other special platforms, size may indeed rule. On most general systems such as x86_64 linux, speed should be the default. Speed is very hard for the user to optimize for because they need platform specific knowledge. Size is easier because you can just choose the integer type which fits your requirements. -- --- 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 email 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-proposals/. ------=_Part_5618_1454122010.1412170938686 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Wednesday, October 1, 2014 9:17:36 AM UTC-4, ri= ck...@hotmail.com wrote:

However, I am dubious about the implementato= r guide of optimizing for speed over size. In contrast, some may prefer to optimize for size over speed.

It's a suggestion, not a mandate. = On embedded or other special platforms, size may indeed rule. On most gener= al systems such as x86_64 linux, speed should be the default. 

Speed is very hard for the user to optimize for because t= hey need platform specific knowledge. Size is easier because you can just c= hoose the integer type which fits your requirements.

--

---
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_5618_1454122010.1412170938686-- .