Deployed 0af45df to master with MkDocs 1.2.4 and mike 1.0.1

master/CHANGELOG/index.html

@@ -1314,6 +1314,9 @@ and this project adheres to <a href="https://semver.org/spec/v2.0.0.html">Semant
 <li>Error messages have been restructured (less newlines) to provide more unified errors. Also <code>pp_oneline/1</code> has been added.</li>
 </ul>
 <h3 id="removed">Removed</h3>
+<ul>
+<li>Support for AEVM has been entirely wiped</li>
+</ul>
 <h2 id="610-2021-10-20"><a href="https://github.com/aeternity/aesophia/compare/v6.0.2...v6.1.0">6.1.0</a> - 2021-10-20</h2>
 <h3 id="added_1">Added</h3>
 <ul>

master/aeso_compiler/index.html

@@ -411,9 +411,7 @@ ErrorString = errorstring()</code></p>
 <p><code>pp_ast</code> - print the AST of the code</p>
 <p><code>pp_types</code> - print information about the types</p>
 <p><code>pp_typed_ast</code> - print the AST with type information at each node</p>
-<p><code>pp_icode</code> - print the internal code structure</p>
 <p><code>pp_assembler</code> - print the generated assembler code</p>
-<p><code>pp_bytecode</code> - print the bytecode instructions</p>
 <h4 id="check_callcontractstring-options-checkret">check_call(ContractString, Options) -&gt; CheckRet</h4>
 <p>Types
 <code>ContractString = string() | binary()
@@ -421,11 +419,6 @@ CheckRet = {ok,string(),{Types,Type | any()},Terms} | {error,Term}
 Types = [Type]
 Type = term()</code>
 Check a call in contract through the <code>__call</code> function.</p>
-<h4 id="sophia_type_to_typerepstring-typerep">sophia_type_to_typerep(String) -&gt; TypeRep</h4>
-<p>Types
-<code>erlang
- {ok,TypeRep} | {error, badtype}</code></p>
-<p>Get the type representation of a type declaration.</p>
 <h4 id="version-ok-version-error-term">version() -&gt; {ok, Version} | {error, term()}</h4>
 <p>Types</p>
 <p><code>erlang

master/sitemap.xml

@@ -2,47 +2,47 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
     <url>
          <loc>None</loc>
-         <lastmod>2022-05-05</lastmod>
+         <lastmod>2022-05-10</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2022-05-05</lastmod>
+         <lastmod>2022-05-10</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2022-05-05</lastmod>
+         <lastmod>2022-05-10</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2022-05-05</lastmod>
+         <lastmod>2022-05-10</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2022-05-05</lastmod>
+         <lastmod>2022-05-10</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2022-05-05</lastmod>
+         <lastmod>2022-05-10</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2022-05-05</lastmod>
+         <lastmod>2022-05-10</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2022-05-05</lastmod>
+         <lastmod>2022-05-10</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>None</loc>
-         <lastmod>2022-05-05</lastmod>
+         <lastmod>2022-05-10</lastmod>
          <changefreq>daily</changefreq>
     </url>
 </urlset>

master/sophia_features/index.html

@@ -1184,8 +1184,6 @@ payable stateful entrypoint buy(to : address) =
     transfer_item(to)
   else
     abort("Value too low")</code></p>
-<p>Note: In the æternity VM (AEVM) contracts and entrypoints were by default
-payable until the Lima release.</p>
 <h2 id="namespaces">Namespaces</h2>
 <p>Code can be split into libraries using the <code>namespace</code> construct. Namespaces
 can appear at the top-level and can contain type and function definitions, but
@@ -1482,7 +1480,7 @@ include "Pair.aes"
 </tbody>
 </table>
 <h2 id="arithmetic">Arithmetic</h2>
-<p>Sophia integers (<code>int</code>) are represented by 256-bit (AEVM) or arbitrary-sized (FATE) signed words and supports the following
+<p>Sophia integers (<code>int</code>) are represented by arbitrary-sized signed words and support the following
 arithmetic operations:
 - addition (<code>x + y</code>)
 - subtraction (<code>x - y</code>)
@@ -1490,18 +1488,13 @@ arithmetic operations:
 - division (<code>x / y</code>), truncated towards zero
 - remainder (<code>x mod y</code>), satisfying <code>y * (x / y) + x mod y == x</code> for non-zero <code>y</code>
 - exponentiation (<code>x ^ y</code>)</p>
-<p>All operations are <em>safe</em> with respect to overflow and underflow. On AEVM they behave as the corresponding
-operations on arbitrary-size integers and fail with <code>arithmetic_error</code> if the
-result cannot be represented by a 256-bit signed word. For example, <code>2 ^ 255</code>
-fails rather than wrapping around to -2²⁵⁵.</p>
-<p>The division and modulo operations also throw an arithmetic error if the
-second argument is zero.</p>
+<p>All operations are <em>safe</em> with respect to overflow and underflow. 
+The division and modulo operations throw an arithmetic error if the
+right-hand operand is zero.</p>
 <h2 id="bit-fields">Bit fields</h2>
 <p>Sophia integers do not support bit arithmetic. Instead there is a separate
 type <code>bits</code>. See the standard library <a href="../sophia_stdlib/#bits">documentation</a>.</p>
-<p>On the AEVM a bit field is represented by a 256-bit word and reading or writing
-a bit outside the 0..255 range fails with an <code>arithmetic_error</code>. On FATE a bit
-field can be of arbitrary size (but it is still represented by the
+<p>A bit field can be of arbitrary size (but it is still represented by the
 corresponding integer, so setting very high bits can be expensive).</p>
 <h2 id="type-aliases">Type aliases</h2>
 <p>Type aliases can be introduced with the <code>type</code> keyword and can be

master/sophia_stdlib/index.html

@@ -986,7 +986,7 @@ namespace Chain =
 <p><code>Chain.block_hash(h : int) : option(bytes(32))</code></p>
 <p>The hash of the block at height <code>h</code>. <code>h</code> has to be within 256 blocks from the
 current height of the chain or else the function will return <code>None</code>.</p>
-<p>NOTE: In AEVM and FATE VM version 1 <code>Chain.block_height</code> was not considered an
+<p>NOTE: In FATE VM version 1 <code>Chain.block_height</code> was not considered an
 allowed height. From FATE VM version 2 (IRIS) it will return the block hash of
 the current generation.</p>
 <h5 id="block_height">block_height</h5>