Remove uncleared merge conflict marks
This commit is contained in:
parent
0ad395a4ed
commit
9cc2a7a0c9
@ -35,7 +35,6 @@ title: Cheat Sheet
|
|||||||
|Variants|<pre><code>type action is<br/>| Increment of int<br/>| Decrement of int</code></pre>|
|
|Variants|<pre><code>type action is<br/>| Increment of int<br/>| Decrement of int</code></pre>|
|
||||||
|Variant *(pattern)* matching|<pre><code>const a: action = Increment(5);<br/>case a of<br/>| Increment(n) -> n + 1<br/>| Decrement(n) -> n - 1<br/>end</code></pre>|
|
|Variant *(pattern)* matching|<pre><code>const a: action = Increment(5);<br/>case a of<br/>| Increment(n) -> n + 1<br/>| Decrement(n) -> n - 1<br/>end</code></pre>|
|
||||||
|Records|<pre><code>type person is record<br/> age: int ;<br/> name: string ;<br/>end<br/><br/>const john : person = record<br/> age = 18;<br/> name = "John Doe";<br/>end<br/><br/>const name: string = john.name;</code></pre>|
|
|Records|<pre><code>type person is record<br/> age: int ;<br/> name: string ;<br/>end<br/><br/>const john : person = record<br/> age = 18;<br/> name = "John Doe";<br/>end<br/><br/>const name: string = john.name;</code></pre>|
|
||||||
<<<<<<< HEAD
|
|
||||||
|Maps|<pre><code>type prices is map(nat, tez);<br/><br/>const prices : prices = map<br/> 10n -> 60mtz;<br/> 50n -> 30mtz;<br/> 100n -> 10mtz;<br/>end<br/><br/>const price: option(tez) = prices[50n];<br/><br/>prices[200n] := 5mtz;</code></pre>|
|
|Maps|<pre><code>type prices is map(nat, tez);<br/><br/>const prices : prices = map<br/> 10n -> 60mtz;<br/> 50n -> 30mtz;<br/> 100n -> 10mtz;<br/>end<br/><br/>const price: option(tez) = prices[50n];<br/><br/>prices[200n] := 5mtz;</code></pre>|
|
||||||
|Contracts & Accounts|<pre><code>const destinationAddress : address = "tz1...";<br/>const contract : contract(unit) = get_contract(destinationAddress);</code></pre>|
|
|Contracts & Accounts|<pre><code>const destinationAddress : address = "tz1...";<br/>const contract : contract(unit) = get_contract(destinationAddress);</code></pre>|
|
||||||
|Transactions|<pre><code>const payment : operation = transaction(unit, amount, receiver);</code></pre>|
|
|Transactions|<pre><code>const payment : operation = transaction(unit, amount, receiver);</code></pre>|
|
||||||
|
@ -9,10 +9,6 @@ There are currently two ways to get started with Ligo, both of those will allow
|
|||||||
|
|
||||||
> 🐳 You can find instructions on how to install Docker [here](https://docs.docker.com/install/).
|
> 🐳 You can find instructions on how to install Docker [here](https://docs.docker.com/install/).
|
||||||
|
|
||||||
<<<<<<< HEAD
|
|
||||||
Easiest way to use LIGO is through the Docker image available at [Docker Hub](https://hub.docker.com/r/ligolang/ligo). Sources for the image can be found on [Gitlab](https://gitlab.com/ligolang/ligo/blob/dev/docker/Dockerfile).
|
|
||||||
You can either run the docker image yourself, or you can setup a global ligo executable as shown below.
|
|
||||||
=======
|
|
||||||
It's easiest to use LIGO through one of its Docker images. You have two options,
|
It's easiest to use LIGO through one of its Docker images. You have two options,
|
||||||
the first is to use our installation script to set up a globally available LIGO
|
the first is to use our installation script to set up a globally available LIGO
|
||||||
executable (see below). This manages the Docker bits for you. The second
|
executable (see below). This manages the Docker bits for you. The second
|
||||||
@ -20,7 +16,6 @@ is to directly use the Docker image available at [Docker Hub](https://hub.docker
|
|||||||
This lets you run multiple versions and keep your installation(s) self contained, but requires more familiarity with Docker.
|
This lets you run multiple versions and keep your installation(s) self contained, but requires more familiarity with Docker.
|
||||||
Sources for the image can be found on [Gitlab](https://gitlab.com/ligolang/ligo/blob/master/docker/Dockerfile).
|
Sources for the image can be found on [Gitlab](https://gitlab.com/ligolang/ligo/blob/master/docker/Dockerfile).
|
||||||
If this is your first time using Docker, you probably want to set up a global ligo executable as shown below.
|
If this is your first time using Docker, you probably want to set up a global ligo executable as shown below.
|
||||||
>>>>>>> Edit installation instructions to emphasize that Docker newbs should use the install script
|
|
||||||
|
|
||||||
### Setting up a globally available `ligo` executable
|
### Setting up a globally available `ligo` executable
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user