[SG16-Unicode] Draft summary of where we are on std::text
Steve Downey
sdowney at gmail.com
Wed Oct 3 05:54:16 CEST 2018
Good catch on the questions. I'll fix consistently one way or the other.
Probably adding '?'
I thought you were done with Boost.Text, but didn't want to over promise
your work.
Allocators. Well I work for Bloomberg, and can tell you without a doubt
that Lakos will No vote if it doesn't support them. I consider it facing
reality. I also use the pre-standard equivalent of pmr frequently, and find
it useful.
Personally, I wouldn't mind seeing scoped allocators vanish, but someone
must want them.
On Tue, Oct 2, 2018, 23:36 Zach Laine <whatwasthataddress at gmail.com> wrote:
> On Tue, Oct 2, 2018 at 10:28 PM Steve Downey <sdowney at gmail.com> wrote:
>
>> Study Group 16 std::text Technical Direction
>>
>
> Thanks so much for doing this, Steve. Two nits: 1) The issues in Areas
> of Discussion are stated as questions, but they currently lack question
> marks. 2) Boost.Text is actually code complete now, but of course will
> probably change during a Boost review.
>
> One crazy guy shouting into the wilderness point: I'm probably alone, but
> I don't think we need, nor do we want, allocators. (Discuss!) I
> understand if I'm alone in this view.
>
> Zach
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.open-std.org/pipermail/unicode/attachments/20181002/3f467a35/attachment.html
More information about the Unicode
mailing list