220 13422 <113390b2-9c74-47e2-a943-5d27dd48bdf1@isocpp.org> article Path: news.gmane.org!not-for-mail From: ricky.65@hotmail.com Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Proposal: Strongly Typed Bitset Date: Wed, 1 Oct 2014 06:17:36 -0700 (PDT) Lines: 92 Approved: news@gmane.org Message-ID: <113390b2-9c74-47e2-a943-5d27dd48bdf1@isocpp.org> References: Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_433_1632799244.1412169456650" X-Trace: ger.gmane.org 1412169465 11237 80.91.229.3 (1 Oct 2014 13:17:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 1 Oct 2014 13:17:45 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDIITWUOTQNRB4P5V6QQKGQE34VLODI@isocpp.org Wed Oct 01 15:17:39 2014 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-pa0-f71.google.com ([209.85.220.71]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XZJml-0000EN-BI for gclcip-std-proposals@m.gmane.org; Wed, 01 Oct 2014 15:17:39 +0200 Original-Received: by mail-pa0-f71.google.com with SMTP id rd3sf4967771pab.10 for ; Wed, 01 Oct 2014 06:17:38 -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: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=hNCz1p2ExPhT0rRAn2vwJDKGsNdS87euqwdrBDuJiF0=; b=WmIzK0kcYZedFIXlJz9gjH2tyFqhmJPmxGInx3rZqeEPonJ0iIsmJ2jB4SHjDmZirt DCYo3/5l/mNyoxKdT8fqkRHbU570tjjpb6tRt3+uqneDNWEtgWbNkA/mepqMAaYQayqI i75iGooNyHrQic/A5pNkJWJpGQGPXlbNiBI0eck6Yrs+lVfQEZ6CxrBukvVLJNy6mqgV B1zwVa8VWpKIa2WuspiaCH5tbQPwMIsS0Q2p4fLJQlASFMPL93Rbg5AEmb9fToDprXec nruv0Wqk9Tw4A9R/xfqEL1RjGrW2hXY87+z1qZqdw/wF16Xm/EgJbH/byP6yfcs/Tjud 0ZsQ== X-Gm-Message-State: ALoCoQkcgPO3o7Je2jMeWnw4p3cakC+CuwivD6JhjM7Ijxs9cdnerbhSSOeNBneFUsFXF03wLSUC X-Received: by 10.68.247.138 with SMTP id ye10mr45105528pbc.6.1412169457922; Wed, 01 Oct 2014 06:17:37 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.140.82.11 with SMTP id g11ls455629qgd.29.gmail; Wed, 01 Oct 2014 06:17:37 -0700 (PDT) X-Received: by 10.140.97.131 with SMTP id m3mr4241qge.28.1412169457125; Wed, 01 Oct 2014 06:17:37 -0700 (PDT) In-Reply-To: X-Original-Sender: ricky.65@hotmail.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:13422 Archived-At: ------=_Part_433_1632799244.1412169456650 Content-Type: text/plain; charset=UTF-8 I welcome this proposal as I feel that it is useful to be able to specify the underlying integral type used for std::bitset. 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. Incidentally, this proposal would make std::bitset consistent with boost::dynamic_bitset which has an analogous template parameter to specify the unsigned integer type in which the bits are stored. It uses "unsigned long" as a default. - Riccardo On Wednesday, October 1, 2014 12:58:01 AM UTC+1, Matthew Fioravante wrote: > > Continued from this thread: > > https://groups.google.com/a/isocpp.org/forum/#!topic/std-proposals/UjNcLLrGwv8 > > Here is the first draft of the proposal: > https://github.com/fmatthew5876/stdcxx-bitset > -- --- 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_433_1632799244.1412169456650 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I welcome this proposal as I feel that it is useful t= o be able to specify the underlying integral type used for std::bitset.

However, I am dubious about the implementator guide o= f optimizing for speed over size. In contrast, some may prefer to optimize for size over speed.
=

Incidentally, this proposal would make std::bitset cons= istent with boost::dynamic_bitset which has an analogous template parameter= to specify the unsigned integer type in which the bits are stored. It uses= "unsigned long" as a default.

- Riccardo 
On Wednesday, October 1, 2014 12:58:01 AM UTC+1, Matthew Fioravante = wrote:

--

---
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_433_1632799244.1412169456650-- .