Topic: Bitsets with extended fuctionalities: strongly
Author: Ville Voutilainen <ville.voutilainen@gmail.com>
Date: Mon, 15 Dec 2014 10:41:08 +0200
Raw View
On 15 December 2014 at 10:38, Vincent Reverdy <vince.rev@gmail.com> wrote:
> Hello.
>
> I would like to know whether proposals has already been made about the
> standardization of a dynamic bitset ?
> I tend to think that static bitset and dynamic bitset (with an ability to
> resize, contrary to the boost version) possibly encoded as arrays and
> vectors of unsigned integral types are currently lacking in the standard
> library (and it seems to me important to stop the use of std::vector<bool>
> as dynamic bitset).
> Is there an interest in that, at least from the community?
> Is there any cons against that?
I can find at least
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2050.pdf
pro tip: google with "site:open-std.org dynamic 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/.
.
Author: Douglas Boffey <douglas.boffey@gmail.com>
Date: Mon, 15 Dec 2014 03:27:02 -0800 (PST)
Raw View
------=_Part_216_1491032752.1418642822557
Content-Type: multipart/alternative;
boundary="----=_Part_217_800786021.1418642822557"
------=_Part_217_800786021.1418642822557
Content-Type: text/plain; charset=UTF-8
On Monday, 15 December 2014 08:38:33 UTC, Vincent Reverdy wrote:
>
> Hello.
>
> I would like to know whether proposals has already been made about the
> standardization of a dynamic bitset ?
> I tend to think that static bitset and dynamic bitset (with an ability to
> resize, contrary to the boost version) possibly encoded as arrays and
> vectors of unsigned integral types are currently lacking in the standard
> library (and it seems to me important to stop the use of std::vector<bool>
> as dynamic bitset).
>
For what reason?
> Is there an interest in that, at least from the community?
> Is there any cons against that?
>
> Thank you very much,
> Vincent
>
--
---
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_217_800786021.1418642822557
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><BR>On Monday, 15 December 2014 08:38:33 UTC, Vincent Reve=
rdy wrote:=20
<BLOCKQUOTE style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3Dgmail_quote>
<DIV dir=3Dltr>Hello.<BR><BR>I would like to know whether proposals has alr=
eady been made about the standardization of a dynamic bitset ?<BR>I tend to=
think that static bitset and dynamic bitset (with an ability to resize, co=
ntrary to the boost version) possibly encoded as arrays and vectors of unsi=
gned integral types are currently lacking in the standard library (and it s=
eems to me important to stop the use of std::vector<bool> as dynamic =
bitset).<BR></DIV></BLOCKQUOTE>
<DIV>For what reason?</DIV>
<DIV> </DIV>
<BLOCKQUOTE style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3Dgmail_quote>
<DIV dir=3Dltr>Is there an interest in that, at least from the community?<B=
R>Is there any cons against that?<BR><BR>Thank you very much,<BR>Vincent<BR=
></DIV></BLOCKQUOTE></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
------=_Part_217_800786021.1418642822557--
------=_Part_216_1491032752.1418642822557--
.
Author: Marc <marc.glisse@gmail.com>
Date: Mon, 15 Dec 2014 05:55:09 -0800 (PST)
Raw View
------=_Part_358_1855351922.1418651709854
Content-Type: multipart/alternative;
boundary="----=_Part_359_1437198614.1418651709854"
------=_Part_359_1437198614.1418651709854
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Le lundi 15 d=C3=A9cembre 2014 09:41:09 UTC+1, Ville Voutilainen a =C3=A9cr=
it :
>
> On 15 December 2014 at 10:38, Vincent Reverdy <vinc...@gmail.com=20
> <javascript:>> wrote:=20
> > Hello.=20
> >=20
> > I would like to know whether proposals has already been made about the=
=20
> > standardization of a dynamic bitset ?=20
> > I tend to think that static bitset and dynamic bitset (with an ability=
=20
> to=20
> > resize, contrary to the boost version) possibly encoded as arrays and=
=20
> > vectors of unsigned integral types are currently lacking in the standar=
d=20
> > library (and it seems to me important to stop the use of=20
> std::vector<bool>=20
> > as dynamic bitset).=20
> > Is there an interest in that, at least from the community?=20
> > Is there any cons against that?=20
>
>
> I can find at least=20
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2050.pdf=20
>
The latest proposal for big integers also includes a form of dynamic bitset=
..
--=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_359_1437198614.1418651709854
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Le lundi 15 d=C3=A9cembre 2014 09:41:09 UTC+1, Ville Vouti=
lainen a =C3=A9crit :<blockquote class=3D"gmail_quote" style=3D"margin=
: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">On 1=
5 December 2014 at 10:38, Vincent Reverdy <<a href=3D"javascript:" targe=
t=3D"_blank" gdf-obfuscated-mailto=3D"BFGubNEPa0EJ" onmousedown=3D"this.hre=
f=3D'javascript:';return true;" onclick=3D"this.href=3D'javascript:';return=
true;">vinc...@gmail.com</a>> wrote:
<br>> Hello.
<br>>
<br>> I would like to know whether proposals has already been made about=
the
<br>> standardization of a dynamic bitset ?
<br>> I tend to think that static bitset and dynamic bitset (with an abi=
lity to
<br>> resize, contrary to the boost version) possibly encoded as arrays =
and
<br>> vectors of unsigned integral types are currently lacking in the st=
andard
<br>> library (and it seems to me important to stop the use of std::vect=
or<bool>
<br>> as dynamic bitset).
<br>> Is there an interest in that, at least from the community?
<br>> Is there any cons against that?
<br>
<br>
<br>I can find at least
<br><a href=3D"http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n205=
0.pdf" target=3D"_blank" onmousedown=3D"this.href=3D'http://www.google.com/=
url?q\75http%3A%2F%2Fwww.open-std.org%2Fjtc1%2Fsc22%2Fwg21%2Fdocs%2Fpapers%=
2F2006%2Fn2050.pdf\46sa\75D\46sntz\0751\46usg\75AFQjCNH-WEOJTuERh03GaSgaKbg=
33iRMgA';return true;" onclick=3D"this.href=3D'http://www.google.com/url?q\=
75http%3A%2F%2Fwww.open-std.org%2Fjtc1%2Fsc22%2Fwg21%2Fdocs%2Fpapers%2F2006=
%2Fn2050.pdf\46sa\75D\46sntz\0751\46usg\75AFQjCNH-WEOJTuERh03GaSgaKbg33iRMg=
A';return true;">http://www.open-std.org/jtc1/<wbr>sc22/wg21/docs/papers/20=
06/<wbr>n2050.pdf</a>
<br></blockquote><div><br>The latest proposal for big integers also include=
s a form of dynamic bitset.<br></div></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
------=_Part_359_1437198614.1418651709854--
------=_Part_358_1855351922.1418651709854--
.
Author: Ville Voutilainen <ville.voutilainen@gmail.com>
Date: Tue, 16 Dec 2014 02:13:42 +0200
Raw View
On 15 December 2014 at 15:55, Marc <marc.glisse@gmail.com> wrote:
> Le lundi 15 d=C3=A9cembre 2014 09:41:09 UTC+1, Ville Voutilainen a =C3=A9=
crit :
>>
>> On 15 December 2014 at 10:38, Vincent Reverdy <vinc...@gmail.com> wrote:
>> > Hello.
>> >
>> > I would like to know whether proposals has already been made about the
>> > standardization of a dynamic bitset ?
>> > I tend to think that static bitset and dynamic bitset (with an ability
>> > to
>> > resize, contrary to the boost version) possibly encoded as arrays and
>> > vectors of unsigned integral types are currently lacking in the standa=
rd
>> > library (and it seems to me important to stop the use of
>> > std::vector<bool>
>> > as dynamic bitset).
>> > Is there an interest in that, at least from the community?
>> > Is there any cons against that?
>>
>>
>> I can find at least
>> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2050.pdf
>
>
> The latest proposal for big integers also includes a form of dynamic bits=
et.
That would be
http://open-std.org/JTC1/SC22/WG21/docs/papers/2014/n4038.html
--=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/.
.
Author: Farid Mehrabi <farid.mehrabi@gmail.com>
Date: Tue, 16 Dec 2014 22:05:13 +0330
Raw View
--001a1135e19ad53dc9050a599f22
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
why not modify or inherit from std::vector<bool>?
It is already specialized from std::vector, and being a vector it is
dynamically sized.
regards,
FM.
2014-12-16 3:43 GMT+03:30 Ville Voutilainen <ville.voutilainen@gmail.com>:
> On 15 December 2014 at 15:55, Marc <marc.glisse@gmail.com> wrote:
> > Le lundi 15 d=C3=A9cembre 2014 09:41:09 UTC+1, Ville Voutilainen a =C3=
=A9crit :
> >>
> >> On 15 December 2014 at 10:38, Vincent Reverdy <vinc...@gmail.com>
> wrote:
> >> > Hello.
> >> >
> >> > I would like to know whether proposals has already been made about t=
he
> >> > standardization of a dynamic bitset ?
> >> > I tend to think that static bitset and dynamic bitset (with an abili=
ty
> >> > to
> >> > resize, contrary to the boost version) possibly encoded as arrays an=
d
> >> > vectors of unsigned integral types are currently lacking in the
> standard
> >> > library (and it seems to me important to stop the use of
> >> > std::vector<bool>
> >> > as dynamic bitset).
> >> > Is there an interest in that, at least from the community?
> >> > Is there any cons against that?
> >>
> >>
> >> I can find at least
> >> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2050.pdf
> >
> >
> > The latest proposal for big integers also includes a form of dynamic
> bitset.
>
> That would be
> http://open-std.org/JTC1/SC22/WG21/docs/papers/2014/n4038.html
>
> --
>
> ---
> 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/.
>
--=20
how am I supposed to end the twisted road of your hair in the dark night??
unless the candle of your face does turn a lamp up on my way!!!
--=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/.
--001a1135e19ad53dc9050a599f22
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"rtl"><div dir=3D"ltr">why not modify or inherit from std::vecto=
r<bool>?</div><div dir=3D"ltr">It is already specialized from std::ve=
ctor, and being a vector =C2=A0it is dynamically sized.</div><div dir=3D"lt=
r"><br></div><div dir=3D"ltr">regards,</div><div dir=3D"ltr">FM.</div></div=
><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><div dir=3D"ltr"=
>2014-12-16 3:43 GMT+03:30 Ville Voutilainen <span dir=3D"ltr"><<a href=
=3D"mailto:ville.voutilainen@gmail.com" target=3D"_blank">ville.voutilainen=
@gmail.com</a>></span>:</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=
=3D"">On 15 December 2014 at 15:55, Marc <<a href=3D"mailto:marc.glisse@=
gmail.com">marc.glisse@gmail.com</a>> wrote:<br>
> Le lundi 15 d=C3=A9cembre 2014 09:41:09 UTC+1, Ville Voutilainen a =C3=
=A9crit :<br>
>><br>
>> On 15 December 2014 at 10:38, Vincent Reverdy <<a href=3D"mailt=
o:vinc...@gmail.com">vinc...@gmail.com</a>> wrote:<br>
>> > Hello.<br>
>> ><br>
>> > I would like to know whether proposals has already been made =
about the<br>
>> > standardization of a dynamic bitset ?<br>
>> > I tend to think that static bitset and dynamic bitset (with a=
n ability<br>
>> > to<br>
>> > resize, contrary to the boost version) possibly encoded as ar=
rays and<br>
>> > vectors of unsigned integral types are currently lacking in t=
he standard<br>
>> > library (and it seems to me important to stop the use of<br>
>> > std::vector<bool><br>
>> > as dynamic bitset).<br>
>> > Is there an interest in that, at least from the community?<br=
>
>> > Is there any cons against that?<br>
>><br>
>><br>
>> I can find at least<br>
>> <a href=3D"http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006=
/n2050.pdf" target=3D"_blank">http://www.open-std.org/jtc1/sc22/wg21/docs/p=
apers/2006/n2050.pdf</a><br>
><br>
><br>
> The latest proposal for big integers also includes a form of dynamic b=
itset.<br>
<br>
</span>That would be<br>
<a href=3D"http://open-std.org/JTC1/SC22/WG21/docs/papers/2014/n4038.html" =
target=3D"_blank">http://open-std.org/JTC1/SC22/WG21/docs/papers/2014/n4038=
..html</a><br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
<br>
---<br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals%2Bunsubscribe@isocpp.org">std-propo=
sals+unsubscribe@isocpp.org</a>.<br>
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank">http://groups.google.com/a/isocpp.org/gro=
up/std-proposals/</a>.<br>
</div></div></blockquote></div><br clear=3D"all"><div><br></div>-- <br><div=
class=3D"gmail_signature"><div dir=3D"ltr">how am I supposed to end the tw=
isted road of=C2=A0 your hair in the dark night??<br>unless the candle of y=
our face does turn a lamp up on my way!!!<br></div></div>
</div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
--001a1135e19ad53dc9050a599f22--
.
Author: Matthew Fioravante <fmatthew5876@gmail.com>
Date: Tue, 16 Dec 2014 16:06:45 -0800 (PST)
Raw View
------=_Part_4368_1728054656.1418774805742
Content-Type: multipart/alternative;
boundary="----=_Part_4369_516985255.1418774805748"
------=_Part_4369_516985255.1418774805748
Content-Type: text/plain; charset=UTF-8
According to this page:
https://botondballo.wordpress.com/2014/11/23/trip-report-c-standards-meeting-in-urbana-champaign-november-2014/
The proposal for strongly typed bitset was rejected. I was not there and
did not present the paper myself so I have no idea why.
On Tuesday, December 16, 2014 1:35:35 PM UTC-5, Farid Mehrabi wrote:
> why not modify or inherit from std::vector<bool>?
> It is already specialized from std::vector, and being a vector it is
> dynamically sized.
>
>
vector<bool> is widely recognized as a big mistake. It might be changed or
deprecated in the future. A true dynamic bitset should use its own type.
--
---
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_4369_516985255.1418774805748
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>According to this page:</div><div><a href=3D"https://=
botondballo.wordpress.com/2014/11/23/trip-report-c-standards-meeting-in-urb=
ana-champaign-november-2014/">https://botondballo.wordpress.com/2014/11/23/=
trip-report-c-standards-meeting-in-urbana-champaign-november-2014/</a></div=
><div> </div><div>The proposal for strongly typed bitset was rejected.=
I was not there and did not present the paper myself so I have no idea why=
..</div><div> </div><div><br>On Tuesday, December 16, 2014 1:35:35 PM U=
TC-5, Farid Mehrabi wrote:</div><blockquote style=3D"margin: 0px 0px 0px 0.=
8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-=
width: 1px; border-left-style: solid;" class=3D"gmail_quote"><div dir=3D"rt=
l"><div dir=3D"ltr">why not modify or inherit from std::vector<bool>?=
</div><div dir=3D"ltr">It is already specialized from std::vector, and bein=
g a vector it is dynamically sized.</div><div dir=3D"ltr"> </div=
></div></blockquote><div> </div><div>vector<bool> is widely=
recognized as a big mistake. It might be changed or deprecated in the=
future. A true dynamic bitset should use its own type. </div></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
------=_Part_4369_516985255.1418774805748--
------=_Part_4368_1728054656.1418774805742--
.
Author: Ville Voutilainen <ville.voutilainen@gmail.com>
Date: Wed, 17 Dec 2014 02:12:50 +0200
Raw View
On 17 December 2014 at 02:06, Matthew Fioravante <fmatthew5876@gmail.com> wrote:
> According to this page:
> https://botondballo.wordpress.com/2014/11/23/trip-report-c-standards-meeting-in-urbana-champaign-november-2014/
>
> The proposal for strongly typed bitset was rejected. I was not there and did
> not present the paper myself so I have no idea why.
The notes are fairly terse. Here's a recommendation, for you and ALL
proposal authors:
once your paper has been dealt with, regardless of the outcome, PLEASE
do contact
whoever you know in the committee and remind them that it would be polite to
notify proposal authors about the handling of their proposals,
including the feedback
and an explanation what happened and why. Quoth the notes:
Beman Dawes presenting, the author is not at the meeting.
BD mentions ABI breakage of changing the template signature. TW
questions the use of small bitsets, "just use an unsigned char". TK
doesn't want to write manual bit-twiddling code and prefers some kind
of abstraction; JY points out that bitfields solve this already.
[Discussions about serialization and guarantees of reading back the
same values that were written out.]
BD: I wouldn't just want 1, 2, 4, 8 bytes. I'd like to see 1, 2, 3, 4,
5, ... bytes. This isn't part of the proposal.
BD: You certainly want to be able to do formatted I/O, operator<<. JY:
That's separate from this proposal. BD: Sure.
TK: Have any codebase owners seen requests for this? TW: I haven't,
and I own our bit manipulation library.
JY: Are we interested in this proposal?
SF WF N WA SA
0 0 5 5 0
--
---
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/.
.
Author: Farid Mehrabi <farid.mehrabi@gmail.com>
Date: Thu, 18 Dec 2014 18:14:49 +0330
Raw View
--047d7bd910c2965d22050a7ea376
Content-Type: text/plain; charset=UTF-8
can u plz explain in more details what is wrong with vector<bool>?
regards,
FM.
2014-12-17 3:36 GMT+03:30 Matthew Fioravante <fmatthew5876@gmail.com>:
>
> According to this page:
>
> https://botondballo.wordpress.com/2014/11/23/trip-report-c-standards-meeting-in-urbana-champaign-november-2014/
>
> The proposal for strongly typed bitset was rejected. I was not there and
> did not present the paper myself so I have no idea why.
>
>
> On Tuesday, December 16, 2014 1:35:35 PM UTC-5, Farid Mehrabi wrote:
>
>> why not modify or inherit from std::vector<bool>?
>> It is already specialized from std::vector, and being a vector it is
>> dynamically sized.
>>
>>
>
> vector<bool> is widely recognized as a big mistake. It might be changed or
> deprecated in the future. A true dynamic bitset should use its own type.
>
--
---
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/.
--
how am I supposed to end the twisted road of your hair in the dark night??
unless the candle of your face does turn a lamp up on my way!!!
--
---
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/.
--047d7bd910c2965d22050a7ea376
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"rtl"><div dir=3D"ltr">can u plz explain in more details what is=
wrong with vector<bool>?</div><div dir=3D"ltr"><br></div><div dir=3D=
"ltr">regards,</div><div dir=3D"ltr">FM.</div></div><div class=3D"gmail_ext=
ra"><div dir=3D"ltr"><br><div class=3D"gmail_quote">2014-12-17 3:36 GMT+03:=
30 Matthew Fioravante <span dir=3D"ltr"><<a href=3D"mailto:fmatthew5876@=
gmail.com" target=3D"_blank">fmatthew5876@gmail.com</a>></span>:<blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 .8ex;border-left:1px #ccc solid=
;border-right:1px #ccc solid;padding-left:1ex;padding-right:1ex"><div>Accor=
ding to this page:</div><div><a href=3D"https://botondballo.wordpress.com/2=
014/11/23/trip-report-c-standards-meeting-in-urbana-champaign-november-2014=
/" target=3D"_blank">https://botondballo.wordpress.com/2014/11/23/trip-repo=
rt-c-standards-meeting-in-urbana-champaign-november-2014/</a></div><div>=C2=
=A0</div><div>The proposal for strongly typed bitset was rejected. I was no=
t there and did not present the paper myself so I have no idea why.</div><s=
pan class=3D""><div>=C2=A0</div><div><br>On Tuesday, December 16, 2014 1:35=
:35 PM UTC-5, Farid Mehrabi wrote:</div><blockquote style=3D"margin:0px 0px=
0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-=
width:1px;border-left-style:solid" class=3D"gmail_quote"><div dir=3D"rtl"><=
div dir=3D"ltr">why not modify or inherit from std::vector<bool>?</di=
v><div dir=3D"ltr">It is already specialized from std::vector, and being a =
vector =C2=A0it is dynamically sized.</div><div dir=3D"ltr">=C2=A0</div></d=
iv></blockquote><div>=C2=A0</div></span><div>vector<bool> is=C2=A0wid=
ely recognized as a=C2=A0big mistake. It might be changed or deprecated in =
the future. A true dynamic bitset should use its own type.=C2=A0</div></blo=
ckquote></div><div class=3D"HOEnZb"><div class=3D"h5">
<p></p>
-- <br>
<br>
--- <br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org" target=3D"_=
blank">std-proposals+unsubscribe@isocpp.org</a>.<br>
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org" target=3D"_blank">std-proposals@isocpp.org</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank">http://groups.google.com/a/isocpp.org/gro=
up/std-proposals/</a>.<br>
</div></div></div><br clear=3D"all"><div><br></div>-- <br><div class=3D"gma=
il_signature"><div dir=3D"ltr">how am I supposed to end the twisted road of=
=C2=A0 your hair in the dark night??<br>unless the candle of your face does=
turn a lamp up on my way!!!<br></div></div>
</div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
--047d7bd910c2965d22050a7ea376--
.
Author: Matthew Fioravante <fmatthew5876@gmail.com>
Date: Thu, 18 Dec 2014 06:54:02 -0800 (PST)
Raw View
------=_Part_253_545198689.1418914442841
Content-Type: multipart/alternative;
boundary="----=_Part_254_1989127921.1418914442841"
------=_Part_254_1989127921.1418914442841
Content-Type: text/plain; charset=UTF-8
On Thursday, December 18, 2014 9:45:12 AM UTC-5, Farid Mehrabi wrote:
>
> can u plz explain in more details what is wrong with vector<bool>?
>
>
In general its considered an abuse of template specialization because
vector<bool> has different semantics from vector<T> for all other type T.
There are also many operations that make sense for collections of bits but
not for vector<T>. It would make sense to either overload these for bitset
classes or make them bitset class member functions.
*http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3864.html*
<http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3864.html>
Here is one good article about it. You can google search to find a lot more
opinions as this is an old topic.
http://isocpp.org/blog/2012/11/on-vectorbool
--
---
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_254_1989127921.1418914442841
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br>On Thursday, December 18, 2014 9:45:12 AM UTC-5, Farid=
Mehrabi wrote:<blockquote style=3D"margin: 0px 0px 0px 0.8ex; padding-left=
: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; borde=
r-left-style: solid;" class=3D"gmail_quote"><div dir=3D"rtl"><div dir=3D"lt=
r">can u plz explain in more details what is wrong with vector<bool>?=
</div><div dir=3D"ltr"> </div></div></blockquote><div> </div><div=
> </div><div>In general its considered an abuse of template specializa=
tion because vector<bool> has different semantics from vector<T>=
; for all other type T.</div><div> </div><div><div>There are also many=
operations that make sense for collections of bits but not for vector<T=
>. It would make sense to either overload these for bitset classes or ma=
ke them bitset class member functions.</div><div><a href=3D"http://www.open=
-std.org/jtc1/sc22/wg21/docs/papers/2014/n3864.html"><u><font color=3D"#000=
080">http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3864.html</fo=
nt></u></a></div></div><div> </div><div>Here is one good article about=
it. You can google search to find a lot more opinions as this is an old to=
pic.</div><div><a href=3D"http://isocpp.org/blog/2012/11/on-vectorbool">htt=
p://isocpp.org/blog/2012/11/on-vectorbool</a></div><div> </div><div>&n=
bsp;</div></div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
------=_Part_254_1989127921.1418914442841--
------=_Part_253_545198689.1418914442841--
.
Author: Ville Voutilainen <ville.voutilainen@gmail.com>
Date: Thu, 18 Dec 2014 17:05:54 +0200
Raw View
On 18 December 2014 at 16:54, Matthew Fioravante <fmatthew5876@gmail.com> wrote:
>
> On Thursday, December 18, 2014 9:45:12 AM UTC-5, Farid Mehrabi wrote:
>>
>> can u plz explain in more details what is wrong with vector<bool>?
>>
>
>
>
> In general its considered an abuse of template specialization because
> vector<bool> has different semantics from vector<T> for all other type T.
>
> There are also many operations that make sense for collections of bits but
> not for vector<T>. It would make sense to either overload these for bitset
> classes or make them bitset class member functions.
> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3864.html
>
> Here is one good article about it. You can google search to find a lot more
> opinions as this is an old topic.
> http://isocpp.org/blog/2012/11/on-vectorbool
An alternate summary:
1) vector<bool> is wonderful. Its only big big problem is that..
2) ..it's not a vector, it's a dynamic bag of bits, so it shouldn't be
a vector specialization.
--
---
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/.
.
Author: Farid Mehrabi <farid.mehrabi@gmail.com>
Date: Fri, 19 Dec 2014 11:31:36 +0330
Raw View
--001a11c383e47dac7b050a8d1f21
Content-Type: text/plain; charset=UTF-8
got it. and its a pretty old issue:
Doc. No.: J16/05-0107 = WG21 N1847 .
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1847.pdf
regards,
FM.
2014-12-18 18:35 GMT+03:30 Ville Voutilainen <ville.voutilainen@gmail.com>:
> On 18 December 2014 at 16:54, Matthew Fioravante <fmatthew5876@gmail.com>
> wrote:
> >
> > On Thursday, December 18, 2014 9:45:12 AM UTC-5, Farid Mehrabi wrote:
> >>
> >> can u plz explain in more details what is wrong with vector<bool>?
> >>
> >
> >
> >
> > In general its considered an abuse of template specialization because
> > vector<bool> has different semantics from vector<T> for all other type T.
> >
> > There are also many operations that make sense for collections of bits
> but
> > not for vector<T>. It would make sense to either overload these for
> bitset
> > classes or make them bitset class member functions.
> > http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3864.html
> >
> > Here is one good article about it. You can google search to find a lot
> more
> > opinions as this is an old topic.
> > http://isocpp.org/blog/2012/11/on-vectorbool
>
>
> An alternate summary:
> 1) vector<bool> is wonderful. Its only big big problem is that..
> 2) ..it's not a vector, it's a dynamic bag of bits, so it shouldn't be
> a vector specialization.
>
> --
>
> ---
> 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/.
>
--
how am I supposed to end the twisted road of your hair in the dark night??
unless the candle of your face does turn a lamp up on my way!!!
--
---
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/.
--001a11c383e47dac7b050a8d1f21
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"rtl"><div dir=3D"ltr">got it. and its a pretty old issue:</div>=
<div dir=3D"ltr"><br></div><div dir=3D"ltr">Doc. No.: =C2=A0J16/05-0107 =3D=
WG21 N1847 .<br></div><div dir=3D"ltr"><font color=3D"#0000ff"><a href=3D"=
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1847.pdf">http://w=
ww.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1847.pdf</a></font><br></d=
iv><div dir=3D"ltr"><br></div><div dir=3D"ltr">regards,</div><div dir=3D"lt=
r">FM.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"=
><div dir=3D"ltr">2014-12-18 18:35 GMT+03:30 Ville Voutilainen <span dir=3D=
"ltr"><<a href=3D"mailto:ville.voutilainen@gmail.com" target=3D"_blank">=
ville.voutilainen@gmail.com</a>></span>:</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><span class=3D"">On 18 December 2014 at 16:54, Matthew Fioravante <=
<a href=3D"mailto:fmatthew5876@gmail.com">fmatthew5876@gmail.com</a>> wr=
ote:<br>
><br>
> On Thursday, December 18, 2014 9:45:12 AM UTC-5, Farid Mehrabi wrote:<=
br>
>><br>
>> can u plz explain in more details what is wrong with vector<boo=
l>?<br>
>><br>
><br>
><br>
><br>
> In general its considered an abuse of template specialization because<=
br>
> vector<bool> has different semantics from vector<T> for al=
l other type T.<br>
><br>
> There are also many operations that make sense for collections of bits=
but<br>
> not for vector<T>. It would make sense to either overload these =
for bitset<br>
> classes or make them bitset class member functions.<br>
> <a href=3D"http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n38=
64.html" target=3D"_blank">http://www.open-std.org/jtc1/sc22/wg21/docs/pape=
rs/2014/n3864.html</a><br>
><br>
> Here is one good article about it. You can google search to find a lot=
more<br>
> opinions as this is an old topic.<br>
> <a href=3D"http://isocpp.org/blog/2012/11/on-vectorbool" target=3D"_bl=
ank">http://isocpp.org/blog/2012/11/on-vectorbool</a><br>
<br>
<br>
</span>An alternate summary:<br>
1) vector<bool> is wonderful. Its only big big problem is that..<br>
2) ..it's not a vector, it's a dynamic bag of bits, so it shouldn&#=
39;t be<br>
a vector specialization.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
<br>
---<br>
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals%2Bunsubscribe@isocpp.org">std-propo=
sals+unsubscribe@isocpp.org</a>.<br>
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br>
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/" target=3D"_blank">http://groups.google.com/a/isocpp.org/gro=
up/std-proposals/</a>.<br>
</div></div></blockquote></div><br clear=3D"all"><div><br></div>-- <br><div=
class=3D"gmail_signature"><div dir=3D"ltr">how am I supposed to end the tw=
isted road of=C2=A0 your hair in the dark night??<br>unless the candle of y=
our face does turn a lamp up on my way!!!<br></div></div>
</div>
<p></p>
-- <br />
<br />
--- <br />
You received this message because you are subscribed to the Google Groups &=
quot;ISO C++ Standard - Future Proposals" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:std-proposals+unsubscribe@isocpp.org">std-proposa=
ls+unsubscribe@isocpp.org</a>.<br />
To post to this group, send email to <a href=3D"mailto:std-proposals@isocpp=
..org">std-proposals@isocpp.org</a>.<br />
Visit this group at <a href=3D"http://groups.google.com/a/isocpp.org/group/=
std-proposals/">http://groups.google.com/a/isocpp.org/group/std-proposals/<=
/a>.<br />
--001a11c383e47dac7b050a8d1f21--
.