random_bytes should include a note that it can generate null bytes about doc-en HOT 5 CLOSED

FWIW, I'm hesitant to make it a warning because I don't want to discourage usage of random_bytes, but I believe it should be noted in some form so that it doesn't come as a surprise.

from doc-en.

Why should this be a warning? Doesn't "bytes" already mean "all bytes"? If you feel a need to clarify this in the manual then I don't it needs to be a warning.

from doc-en.

Removed the "warning" wording because, agreed, it shouldn't be a warning, but I think it should be noted at least.

from doc-en.

Can you elaborate on why null bytes deserves special mention for this function? We don't ordinarily do that for other functions whose return value can contain null bytes.

from doc-en.

I also agree with other replies here, there is no need to document that null bytes are possible, this is implied by the type "byte" being an 8-bit value from 0-255. All values in this range are valid byte values, including 0. If the function was random_char or similar then it would warrant such warnings, but this is not what it is.

from doc-en.