220 29316 article Path: news.gmane.org!.POSTED!not-for-mail From: Dejan Milosavljevic Newsgroups: gmane.comp.lang.c++.isocpp.proposals Subject: Re: Re: std::byte thoughts Date: Tue, 1 Nov 2016 21:28:21 +0100 Lines: 112 Approved: news@gmane.org Message-ID: References: <7da80620-e4bd-40eb-a4ec-4f3c2dcb2c98@isocpp.org> <004be1ec-6455-4844-b704-7961ea745773@isocpp.org> Reply-To: std-proposals@isocpp.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c0554b06c02af0540432aa4 X-Trace: blaine.gmane.org 1478032134 12349 195.159.176.226 (1 Nov 2016 20:28:54 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 1 Nov 2016 20:28:54 +0000 (UTC) To: std-proposals@isocpp.org Original-X-From: std-proposals+bncBDFYFDOFWUGBBZXV4PAAKGQE4J4XWTQ@isocpp.org Tue Nov 01 21:28:49 2016 Return-path: Envelope-to: gclcip-std-proposals@m.gmane.org Original-Received: from mail-oi0-f69.google.com ([209.85.218.69]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c1ffQ-00080H-V4 for gclcip-std-proposals@m.gmane.org; Tue, 01 Nov 2016 21:28:21 +0100 Original-Received: by mail-oi0-f69.google.com with SMTP id 128sf162128541oih.1 for ; Tue, 01 Nov 2016 13:28:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isocpp-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :x-original-sender:x-original-authentication-results:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=17R0WG3GmIsJm9uMQKlBZQTeG89Bg/GCBPMAjaOBg5s=; b=W4rMlRHtKhaiegHYp1NzUsN8q3I6qeiN41HtNoIi8HNQOelelN49xbf9OI9lNVdxEF eAj48kggdDR5SGAmQbdLBHs1NiIex/fbE8RoHFppEjTQ5s0A+vmFc9JnvlqRPpw7rRTF /6yypxlQ5ey2xFmCkp2PimqbpYOM29a2kuHSElpOQPDvey3cPWzCP3XKTU79PGreQK3e /wxNk8lPfemvsKHhkKKMQCVDJ15gyekDS0lbL9ObAhb1vWdMz2DIbBaCsog4ARn1ofkW DEDZXLXZfL3xJOwusxyB8KbU5JNFSNPbe7Jeor/prJ+C9RM/aS4D+J6L1EkAdFfmGOzH 4s9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :list-subscribe:list-unsubscribe; bh=17R0WG3GmIsJm9uMQKlBZQTeG89Bg/GCBPMAjaOBg5s=; b=UbMHKOObxacxBFr9Am/x1Fzvbz71SI4QGW4T9KGOYzENaztfIRosIy5BVSUeCfl0g4 fLJlbwie6sBMFmvaLdKjmZ2CLx4TOvOxVU290xFNrgTfXWF5PObQzjfv4+OYqfViqgO2 CJtX7CmH9q4vMty7s1Ityu9D2HN26k0RhyNsvYJtu0fKmwIuNfrBiMAprp5zxVrRPxav kY3Qhz3C7/zlm3RP9ddVs+rrATtV11dBkkiKNRKu97cBLkulPnL28yyOJ+bUcH+dWatx upGlmYsYaJPKKbhiwRc4vkZsnT21nSFxHU4k+5r2qjTp+wCw658R9ifkjMhd6t8TQWBW O2Zg== X-Gm-Message-State: ABUngvd182QXM6EaE+FiZxD1HYVN3kCIweEB9uF+1G6bG4SAAZ7Yh45/qAnS6MY2ULI+gA== X-Received: by 10.157.9.240 with SMTP id 45mr37418otz.30.1478032103468; Tue, 01 Nov 2016 13:28:23 -0700 (PDT) X-BeenThere: std-proposals@isocpp.org Original-Received: by 10.157.12.9 with SMTP id 9ls2961101otr.43.gmail; Tue, 01 Nov 2016 13:28:22 -0700 (PDT) X-Received: by 10.31.180.132 with SMTP id d126mr29825018vkf.139.1478032102668; Tue, 01 Nov 2016 13:28:22 -0700 (PDT) Original-Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com. [2607:f8b0:400d:c09::234]) by mx.google.com with ESMTPS id j1si14621345vkf.69.2016.11.01.13.28.22 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Nov 2016 13:28:22 -0700 (PDT) Received-SPF: pass (google.com: domain of dmilos@gmail.com designates 2607:f8b0:400d:c09::234 as permitted sender) client-ip=2607:f8b0:400d:c09::234; Original-Received: by mail-qk0-x234.google.com with SMTP id q130so94196588qke.1 for ; Tue, 01 Nov 2016 13:28:22 -0700 (PDT) X-Received: by 10.55.96.194 with SMTP id u185mr27067541qkb.140.1478032102259; Tue, 01 Nov 2016 13:28:22 -0700 (PDT) Original-Received: by 10.12.162.98 with HTTP; Tue, 1 Nov 2016 13:28:21 -0700 (PDT) In-Reply-To: <004be1ec-6455-4844-b704-7961ea745773@isocpp.org> X-Original-Sender: dmilos@gmail.com X-Original-Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com; spf=pass (google.com: domain of dmilos@gmail.com designates 2607:f8b0:400d:c09::234 as permitted sender) smtp.mailfrom=dmilos@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=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:29316 Archived-At: --94eb2c0554b06c02af0540432aa4 Content-Type: text/plain; charset=UTF-8 In there is uint8_t. So far it is optional. In GCC and MSVS this type exists. On Mon, Oct 31, 2016 at 2:58 PM, wrote: > Off the top of my head. > - Native byte is out of question, because it will break existing code > which defined something else behind it. > Also it will be very confusing to have two basic types with *exactly* the > same properties and not be "shortcuts" for one another. > - byte_t will break code as well. > > Also, you can always do a 'using std:byte' in your code and you are all > set. > > That said, it is probably more correct to be called std::byte_t like > std::size_t, std::nullptr_t, std::nullopt_t, std::align_val_t > > The last one is *particularly* *relevant* because it is already just enum > class align_val_t : size_t {}; so the overloading can pick it up > > byte is much more akin to these basic types, then to string, vector or > map, which don't have a _t > > > > > -- > 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. > To view this discussion on the web visit https://groups.google.com/a/ > isocpp.org/d/msgid/std-proposals/004be1ec-6455-4844- > b704-7961ea745773%40isocpp.org > > . > -- 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. To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAEfefmx0QMVa504JmgiOrPbq-xKjTpa5ahD9MyqrM1izU-Mkkg%40mail.gmail.com. --94eb2c0554b06c02af0540432aa4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
In <cstdint> there=C2=A0is uint8_t.
S= o far it is optional.
In GCC and MSVS this type exists.


On Mon,= Oct 31, 2016 at 2:58 PM, <mihailnajdenov@gmail.com>= wrote:
Off the top= of my head.
=C2=A0- Native byte is out of question,=C2=A0becaus= e it will break existing code which defined something else behind it.
Also it will be very confusing to have two basic types with exactl= y=C2=A0the same properties and not be "shortcuts" for one ano= ther.
=C2=A0- byte_t will break code as well.

Also, you can always do a 'using std:byte' in your code=C2=A0= and you are all set.

That said, it is probably mo= re correct to be called std::byte_t like std::size_t, std::nullptr_t, std::= nullopt_t, std::align_val_t

The last one is <= i>particularly relevant because it is already just enum class al= ign_val_t : size_t {}; so the overloading can pick it up
byte is much=C2=A0more akin to these basic types, then to= string, vector or map, which don't have a _t




--
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-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
 To view this discussion on the web visit = https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/004b= e1ec-6455-4844-b704-7961ea745773%40isocpp.org.

--
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.
To view this discussion on the web visit htt= ps://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CAEfefmx0QMVa504J= mgiOrPbq-xKjTpa5ahD9MyqrM1izU-Mkkg%40mail.gmail.com.
--94eb2c0554b06c02af0540432aa4-- .