Merge pull request #8805 from ethereum/solidity-upgrade-documentation

[BREAKING] Update documentation for solidity-upgrade 0.7.0

docs/070-breaking-changes.rst

@@ -0,0 +1,17 @@
+********************************
+Solidity v0.7.0 Breaking Changes
+********************************
+
+This section highlights the main breaking changes introduced in Solidity
+version 0.7.0, along with the reasoning behind the changes and how to update
+affected code.
+For the full list check
+`the release changelog <https://github.com/ethereum/solidity/releases/tag/v0.7.0>`_.
+
+How to update your code
+=======================
+
+This section gives detailed instructions on how to update prior code for every breaking change.
+
+* Change ``f.value(...)()`` to ``f{value: ...}()``. Similarly ``(new C).value(...)()`` to
+  ``(new C){value: ...}()`` and ``f.gas(...)()`` to ``f{gas: ...}()``.

docs/index.rst

@@ -127,6 +127,7 @@ Contents
 
    050-breaking-changes.rst
    060-breaking-changes.rst
+   070-breaking-changes.rst
    natspec-format.rst
    security-considerations.rst
    resources.rst

docs/internals/layout_in_storage.rst

@@ -71,7 +71,7 @@ So for the following contract snippet
 the position of ``data[4][9].b`` is at ``keccak256(uint256(9) . keccak256(uint256(4) . uint256(1))) + 1``::
 
 
-    pragma solidity >=0.4.0 <0.7.0;
+    pragma solidity >=0.4.0 <0.8.0;
 
 
     contract C {
@@ -171,7 +171,7 @@ value and reference types, types that are encoded packed, and nested types.
 
 .. code::
 
-    pragma solidity >=0.4.0 <0.7.0;
+    pragma solidity >=0.4.0 <0.8.0;
     contract A {
         struct S {
             uint128 a;

docs/using-the-compiler.rst

@@ -571,9 +571,16 @@ Available upgrade modules
 | ``override``    | 0.6.0   | When overriding a function or modifier, the new  |
 |                 |         | keyword ``override`` must be used.               |
 +-----------------+---------+--------------------------------------------------+
+| ``dotsyntax``   | 0.7.0   | The following syntax is deprecated:              |
+|                 |         | ``f.gas(...)()``, ``f.value(...)()`` and         |
+|                 |         | ``(new C).value(...)()``. Replace these calls by |
+|                 |         | ``f{gas: ..., value: ...}()`` and                |
+|                 |         | ``(new C){value: ...}()``.                       |
++-----------------+---------+--------------------------------------------------+
 
-Please read :doc:`0.5.0 release notes <050-breaking-changes>` and
+Please read :doc:`0.5.0 release notes <050-breaking-changes>`,
-:doc:`0.6.0 release notes <060-breaking-changes>` for further details.
+:doc:`0.6.0 release notes <060-breaking-changes>` and
+:doc:`0.7.0 release notes <070-breaking-changes>` for further details.
 
 Synopsis
 ~~~~~~~~
@@ -668,8 +675,9 @@ do not need to specify the ``--modules`` option.
     Found 0 errors.
     Found 0 upgrades.
 
-The above performs a dry-ran upgrade on the given file and logs statistics after all.
+The above performs a dry-run upgrade on the given file and logs statistics at
-In this case, the upgrade was successful and no further adjustments are needed.
+the end. In this case, the upgrade was successful and no further adjustments are
+needed.
 
 Finally, you can run the upgrade and also write to the source file.