ea69e0b4b6
743: Bump self_update from 0.25.0 to 0.26.0 r=collinc97 a=dependabot-preview[bot] Bumps [self_update](https://github.com/jaemk/self_update) from 0.25.0 to 0.26.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/jaemk/self_update/blob/master/CHANGELOG.md">self_update's changelog</a>.</em></p> <blockquote> <h2>[0.26.0]</h2> <h3>Added</h3> <h3>Changed</h3> <ul> <li>Clean up dangling temporary directories on Windows.</li> </ul> <h3>Removed</h3> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/jaemk/self_update/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://api.dependabot.com/badges/compatibility_score?dependency-name=self_update&package-manager=cargo&previous-version=0.25.0&new-version=0.26.0)](https://dependabot.com/compatibility-score/?dependency-name=self_update&package-manager=cargo&previous-version=0.25.0&new-version=0.26.0) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) </details> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com> |
||
---|---|---|
.cargo | ||
.circleci | ||
.github | ||
.resources | ||
asg | ||
ast | ||
compiler | ||
examples | ||
gadgets | ||
imports | ||
input | ||
leo | ||
linter | ||
package | ||
parser | ||
state | ||
synthesizer | ||
tests | ||
.codecov.yml | ||
.gitignore | ||
.licenserc.json | ||
.rustfmt.toml | ||
.rusty-hook.toml | ||
bors.toml | ||
Cargo.lock | ||
Cargo.toml | ||
CONTRIBUTING.md | ||
DEVELOPMENT.md | ||
FAQs.md | ||
LICENSE.md | ||
README.md | ||
SECURITY.md |
The Leo Programming Language
Leo is a functional, statically-typed programming language built for writing private applications.
Table of Contents
1. Overview
Welcome to the Leo programming language.
Leo provides a high-level language that abstracts low-level cryptographic concepts and makes it easy to integrate private applications into your stack. Leo compiles to circuits making zero-knowledge proofs practical.
The syntax of Leo is influenced by traditional programming languages like JavaScript, Scala, and Rust, with a strong emphasis on readability and ease-of-use. Leo offers developers with tools to sanity check circuits including unit tests, integration tests, and console functions.
Leo is one part of a greater ecosystem for building private applications on Aleo. If your goal is to build a user experience on the web that is both truly personal and truly private, then we recommend downloading the Aleo Studio IDE and checking out the Aleo Package Manager.
2. Build Guide
2.1 Install Rust
We recommend installing Rust using rustup. You can install rustup
as follows:
-
macOS or Linux:
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
-
Windows (64-bit):
Download the Windows 64-bit executable and follow the on-screen instructions.
-
Windows (32-bit):
Download the Windows 32-bit executable and follow the on-screen instructions.
2.2a Build from Crates.io
We recommend installing Leo this way. In your terminal, run:
cargo install leo-lang
Now to use Leo, in your terminal, run:
leo
2.2b Build from Source Code
Alternatively, you can install Leo by building from the source code as follows:
# Download the source code
git clone https://github.com/AleoHQ/leo
cd leo
# Build in release mode
$ cargo build --release
This will generate an executable under the ./target/release
directory. To run Leo, run the following command:
./target/release/leo
3. Quick Start
Use the Leo CLI to create a new project
# create a new `hello_world` Leo project
leo new hello_world
cd hello_world
# build & setup & prove & verify
leo run
The leo new
command creates a new Leo project with a given name.
The leo run
command will compile the main program, generate keys for a trusted setup, fetch inputs, generate a proof and verify it.
Congratulations! You've just run your first Leo program.
4. Documentation
5. Contributing
Please see our guidelines in the developer documentation
Thank you for helping make Leo better!