From f4ee72494f5e6baa7ccf73bb8309f8e1b59446f6 Mon Sep 17 00:00:00 2001 From: Chris Ward Date: Wed, 19 Dec 2018 17:51:33 +0100 Subject: Remove explicit conversion FAQ item, covered elsewhere --- docs/frequently-asked-questions.rst | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/docs/frequently-asked-questions.rst b/docs/frequently-asked-questions.rst index 2cc082b4..02bf908b 100644 --- a/docs/frequently-asked-questions.rst +++ b/docs/frequently-asked-questions.rst @@ -178,16 +178,6 @@ does not fit inside this range, it is truncated. These truncations can have above is necessary to avoid certain attacks. -Why are explicit conversions between fixed-size bytes types and integer types failing? -====================================================================================== - -Since version 0.5.0 explicit conversions between fixed-size byte arrays and integers are only allowed, -if both types have the same size. This prevents unexpected behaviour when truncating or padding. -Such conversions are still possible, but intermediate casts are required that make the desired -truncation and padding convention explicit. See :ref:`types-conversion-elementary-types` for a full -explanation and examples. - - Why can number literals not be converted to fixed-size bytes types? =================================================================== -- cgit