789. xor_combine_engine(result_type) should be explicit

Section: 99 [rand.adapt.xor] Status: CD1 Submitter: P.J. Plauger Opened: 2008-02-09 Last modified: 2016-02-10

Priority: Not Prioritized

View all other issues in [rand.adapt.xor].

View all issues with CD1 status.

Discussion:

xor_combine_engine(result_type) should be explicit. (Obvious oversight.)

[ Bellevue: ]

Non-controversial. Bill is right, but Fermilab believes that this is easy to use badly and hard to use right, and so it should be removed entirely. Got into TR1 by well defined route, do we have permission to remove stuff? Should probably check with Jens, as it is believed he is the originator. Broad consensus that this is not a robust engine adapter.

Proposed resolution:

Remove xor_combine_engine from synopsis of 29.6.2 [rand.synopsis].

Remove 99 [rand.adapt.xor] xor_combine_engine.