Date: Wed, 12 May 2021 17:54:03 -0700
On Wednesday, 12 May 2021 15:14:29 PDT Arthur O'Dwyer via Std-Proposals wrote:
> Even better: Get the source code of `stable_uniform_int_distribution` from
> a third-party GitHub repository, where if you ever do discover that the
> behavior differs across platforms, you can just file a bug and it's clearly
> on them to fix it. If you rely on the Standard Library for this stuff, then
> you have nowhere (or rather, five or six places) to file bug reports when
> it doesn't work.
>
> I see many reasons this should be on GitHub, and no reason this should be
> in the Standard Library.
Agreed. If you want a specific implementation even if not optimal, then you
don't really want the standard library.
I don't understand why the algorithm for std::seed_seq is specified. Not that
std::seed_seq is actually useful (see proposal about seeding engines).
> Even better: Get the source code of `stable_uniform_int_distribution` from
> a third-party GitHub repository, where if you ever do discover that the
> behavior differs across platforms, you can just file a bug and it's clearly
> on them to fix it. If you rely on the Standard Library for this stuff, then
> you have nowhere (or rather, five or six places) to file bug reports when
> it doesn't work.
>
> I see many reasons this should be on GitHub, and no reason this should be
> in the Standard Library.
Agreed. If you want a specific implementation even if not optimal, then you
don't really want the standard library.
I don't understand why the algorithm for std::seed_seq is specified. Not that
std::seed_seq is actually useful (see proposal about seeding engines).
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DPG Cloud Engineering
Received on 2021-05-12 19:54:09