diff options
author | Chris Ward <chris.ward@ethereum.org> | 2018-12-20 00:51:33 +0800 |
---|---|---|
committer | Chris Ward <chris.ward@ethereum.org> | 2019-01-14 20:29:07 +0800 |
commit | f4ee72494f5e6baa7ccf73bb8309f8e1b59446f6 (patch) | |
tree | a9dfd064eee7aa914abd317c9c930bbe116a00c2 | |
parent | 051df31924e7d10351e9a3abd4becd3631e83391 (diff) | |
download | dexon-solidity-f4ee72494f5e6baa7ccf73bb8309f8e1b59446f6.tar.gz dexon-solidity-f4ee72494f5e6baa7ccf73bb8309f8e1b59446f6.tar.zst dexon-solidity-f4ee72494f5e6baa7ccf73bb8309f8e1b59446f6.zip |
Remove explicit conversion FAQ item, covered elsewhere
-rw-r--r-- | docs/frequently-asked-questions.rst | 10 |
1 files changed, 0 insertions, 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? =================================================================== |