aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorchriseth <chris@ethereum.org>2019-01-14 21:13:07 +0800
committerGitHub <noreply@github.com>2019-01-14 21:13:07 +0800
commit2d4951edf73c7b2e8c1d91628f3e7ec22a2ea8da (patch)
tree8c3083eb5ad3b7878073e36f417addfb3e7e3b83
parent185d221909077e90de62c20ecba2a7ae35daca3c (diff)
parentf4ee72494f5e6baa7ccf73bb8309f8e1b59446f6 (diff)
downloaddexon-solidity-2d4951edf73c7b2e8c1d91628f3e7ec22a2ea8da.tar.gz
dexon-solidity-2d4951edf73c7b2e8c1d91628f3e7ec22a2ea8da.tar.zst
dexon-solidity-2d4951edf73c7b2e8c1d91628f3e7ec22a2ea8da.zip
Merge pull request #5790 from ethereum/faq-explicit-conversion
[DOCS] Remove explicit conversion FAQ item, covered elsewhere
-rw-r--r--docs/frequently-asked-questions.rst10
1 files changed, 0 insertions, 10 deletions
diff --git a/docs/frequently-asked-questions.rst b/docs/frequently-asked-questions.rst
index 20c01e5c..4635d577 100644
--- a/docs/frequently-asked-questions.rst
+++ b/docs/frequently-asked-questions.rst
@@ -152,16 +152,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?
===================================================================