Skip to content

Should BlockRngCore::Results also be AsMut? #376

@pitdicker

Description

@pitdicker

I think adding the bound now is no big deal, and it could allow for a BlockRng-like implementation that zeros out used results.

On the other hand I don't see much value in modifying / using Results from the 'outside'. Anything that can read the results field of BlockRng can probably also read the internal state of the RNG, so why take extra precautions?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions