mirror of
https://github.com/ethereum/solidity
synced 2023-10-03 13:03:40 +00:00
Merge pull request #5790 from ethereum/faq-explicit-conversion
[DOCS] Remove explicit conversion FAQ item, covered elsewhere
This commit is contained in:
commit
2d4951edf7
@ -152,16 +152,6 @@ does not fit inside this range, it is truncated. These truncations can have
|
|||||||
above is necessary to avoid certain attacks.
|
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?
|
Why can number literals not be converted to fixed-size bytes types?
|
||||||
===================================================================
|
===================================================================
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user