Merge pull request #259 from huff-language/stage

Stage
huff-language · Jul 8, 2023 · d301bff · d301bff
2 parents 94c34e4 + a7403c9
commit d301bff
Show file tree

Hide file tree

Showing 87 changed files with 3,100 additions and 2,547 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/README.md b/README.md
@@ -4,7 +4,6 @@
 
 > `huff-rs` is a [Huff](https://github.com/huff-language) compiler built in rust.
 
-
 ## What is a Huff?
 
 Huff is a low-level programming language designed for developing highly optimized smart contracts that run on the Ethereum Virtual Machine (EVM). Huff does not hide the inner workings of the EVM. Instead, Huff exposes its programming stack to the developer for manual manipulation.
@@ -17,7 +16,6 @@ While EVM experts can use Huff to write highly-efficient smart contracts for use
 
 To dive deeper into [Huff](https://github.com/huff-language), visit the [Official Huff Docs](https://huff.sh)(also available on [github](https://github.com/huff-language/huff-docs)).
 
-
 ## Installation
 
 _Something not working? Send a message in [discord](https://discord.huff.sh)._
@@ -33,14 +31,16 @@ To avoid redirecting the script directly into bash, download and run the [huffup
 To install the Huff compiler, simply run `huffup`.
 
 If you have the old [huffc (TypeScript version)](https://github.com/huff-language/huffc) npm package installed globally, you can remove it with:
+
 ```bash
 sudo yarn global remove huffc
 ```
 
-To make sure you are running the rust version, you can run `huffc --version` and it should respond with `huff_cli <version>`.  If it responds with `2.0.0` that means you are running the Typescript version.
+To make sure you are running the rust version, you can run `huffc --version` and it should respond with `huff_cli <version>`. If it responds with `2.0.0` that means you are running the Typescript version.
+
 ```bash
 $ huffc --version
-huff_cli 0.3.1
+huff_cli 0.3.2
 ```
 
 **Alternatively**
@@ -59,43 +59,41 @@ OR
 cargo install --git https://raw.githubusercontent.com/huff-language/huff-rs --locked huff_cli
 ```
 
-
 ## How Fast?
 
 **Compilation Benchmarks**
 
 | Compiler                         | Cold (No Cache) | Light Cache | Deep Cache | Full Cache |
 | -------------------------------- | --------------- | ----------- | ---------- | ---------- |
-| [huff-language/huff-rs][huff-rs] |           XXXms |       XXXms |      XXXms |      XXXms |
-| [huff-language/huffc][huffc]     |           XXXms |       XXXms |      XXXms |      XXXms |
+| [huff-language/huff-rs][huff-rs] | XXXms           | XXXms       | XXXms      | XXXms      |
+| [huff-language/huffc][huffc]     | XXXms           | XXXms       | XXXms      | XXXms      |
 
 _Note: Compilation benchmarks were performed on [huff-examples erc20](https://github.com/huff-language/huff-examples/tree/main/erc20/contracts/ERC20.huff)._
 
-
 ## Architecture
 
 ![Huff Compiler Architecture](./assets/huffc.png)
 
-
 ## Modules
-* [huff_core](./huff_core): The core module to huff-rs. Resolves source file paths, executes compilation, and exports artifacts.
-* [huff_cli](./huff_cli): The command line interface for the Huff compiler.
-* [huff_js](./huff_js): A wasm compatible interface to the Huff compiler for JavaScript bindings.
-* [huff_lexer](./huff_lexer): Takes in the source of a `.huff` file and generates a vector of `Token`s.
-* [huff_parser](./huff_parser): Crafts a `Contract` AST from the vector of `Token`s generated by [huff_lexer](./huff_lexer).
-* [huff_codegen](./huff_codegen): EVM Bytecode generation module that accepts an AST generated by [huff_parser](./huff_parser).
-* [huff_utils](./huff_utils): Various utilities and types used by all modules.
-* [huffup](./huffup): Update or revert to a specific huff-rs branch with ease. (Forked from [foundry](https://github.com/foundry-rs/foundry))
 
+- [huff_core](./huff_core): The core module to huff-rs. Resolves source file paths, executes compilation, and exports artifacts.
+- [huff_cli](./huff_cli): The command line interface for the Huff compiler.
+- [huff_js](./huff_js): A wasm compatible interface to the Huff compiler for JavaScript bindings.
+- [huff_lexer](./huff_lexer): Takes in the source of a `.huff` file and generates a vector of `Token`s.
+- [huff_parser](./huff_parser): Crafts a `Contract` AST from the vector of `Token`s generated by [huff_lexer](./huff_lexer).
+- [huff_codegen](./huff_codegen): EVM Bytecode generation module that accepts an AST generated by [huff_parser](./huff_parser).
+- [huff_utils](./huff_utils): Various utilities and types used by all modules.
+- [huffup](./huffup): Update or revert to a specific huff-rs branch with ease. (Forked from [foundry](https://github.com/foundry-rs/foundry))
 
 ## Contributing
 
 All contributions are welcome! We want to make contributing to this project as easy and transparent as possible, whether it's:
-  - Reporting a bug
-  - Discussing the current state of the code
-  - Submitting a fix
-  - Proposing new features
-  - Becoming a maintainer
+
+- Reporting a bug
+- Discussing the current state of the code
+- Submitting a fix
+- Proposing new features
+- Becoming a maintainer
 
 We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/huff-language/huff-rs/issues/new); it's that easy!
 
@@ -141,7 +139,6 @@ When the PR checklist isn't complete, it is **highly** recommended to make it a
 
 For breaking changes: make sure to edit the [excalidraw asset](https://excalidraw.com/#json=9YvTZp-rY9NOQnX9TC8Dz,sVM8vpgvQqGiXNXrBNshTg) and export the file to [./assets/huffc.excalidraw](./assets/huffc.excalidraw) along with an image to [./assets/huffc.png](./assets/huffc.png).
 
-
 ## Safety
 
 > **Warning**
@@ -150,13 +147,13 @@ For breaking changes: make sure to edit the [excalidraw asset](https://excalidra
 > Expect rapid iteration and **use at your own risk**.
 >
 > This code is **not designed for safety**.
+>
 > - There are untested invariants in the code that may break.
 > - **You can easily shoot yourself in the foot if you're not careful.**
 > - You should thoroughly read the documentation and examples.
 >
 > We **do not give any warranties** and **will not be liable for any loss** incurred through any use of this codebase.
 
-
 ## Acknowledgements
 
 The original [Huff Language](https://github.com/huff-language) compiler: [`huffc`](https://github.com/huff-language/huffc).

diff --git a/huff_cli/Cargo.toml b/huff_cli/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "huff_cli"
-version = "0.3.1"
+version = "0.3.2"
 edition = "2021"
 authors = ["refcell", "clabby", "exp.table", "maddiaa"]
 readme = "README.md"
@@ -17,6 +17,7 @@ huff_core = { path = "../huff_core", version = "0.x.x" }
 huff_codegen = { path = "../huff_codegen", version = "0.x.x" }
 huff_utils = { path = "../huff_utils", version = "0.x.x" }
 huff_tests = { path = "../huff_tests", version = "0.x.x" }
+comfy-table = "6.0.0"
 tracing = "0.1.34"
 ethers-core = "1.0.2"
 yansi = "0.5.1"

diff --git a/huff_cli/README.md b/huff_cli/README.md
@@ -5,43 +5,87 @@ The `huffc` CLI is written using [clap's](https://docs.rs/clap) [derive feature]
 ## huffc
 
 ```
-huffc 0.3.1
+huffc 0.3.2
 Huff Language Compiler built in Pure Rust.
 
 USAGE:
-    huffc [OPTIONS] [--] [PATH]
+    huffc [OPTIONS] [PATH] [SUBCOMMAND]
 
 ARGS:
     <PATH>    The contract(s) to compile
 
 OPTIONS:
-    -a, --artifacts                       Whether to generate artifacts or not
-    -b, --bytecode                        Generate and log bytecode
-    -d, --output-directory <OUTPUTDIR>    The output directory [default: ./artifacts]
-    -g, --interface                       Generate solidity interface for a Huff artifact
-    -h, --help                            Print help information
-    -i, --inputs <INPUTS>...              The input constructor arguments
-    -n, --interactive                     Interactively input the constructor args
-    -o, --output <OUTPUT>                 The output file path
-    -p, --print                           Prints out to the terminal
-    -r, --bin-runtime                     Generate and log runtime bytecode
-    -s, --source-path <SOURCE>            The contracts source path [default: ./contracts]
-    -v, --verbose                         Verbose output
-    -V, --version                         Print version information
-    -z, --optimize                        Optimize compilation [WIP]
+    -a, --artifacts
+            Whether to generate artifacts or not
+
+    -b, --bytecode
+            Generate and log bytecode
+
+    -c, --constants <CONSTANTS>...
+            Override / set constants for the compilation environment
+
+    -d, --output-directory <OUTPUTDIR>
+            The output directory [default: ./artifacts]
+
+    -e, --evm-version <EVM_VERSION>
+            Set the EVM version
+
+    -g, --interface [<INTERFACE>...]
+            Generate solidity interface for a Huff artifact
+
+    -h, --help
+            Print help information
+
+    -i, --inputs <INPUTS>...
+            The input constructor arguments
+
+    -l, --label-indices
+            Prints out the jump label PC indices for the specified contract
+
+    -m, --alt-main <ALTERNATIVE_MAIN>
+            Compile a specific macro
+
+    -n, --interactive
+            Interactively input the constructor args
+
+    -o, --output <OUTPUT>
+            The output file path
+
+    -p, --print
+            Prints out to the terminal
+
+    -r, --bin-runtime
+            Generate and log runtime bytecode
+
+    -s, --source-path <SOURCE>
+            The contracts source path [default: ./contracts]
+
+    -t, --alt-constructor <ALTERNATIVE_CONSTRUCTOR>
+            Compile a specific constructor macro
+
+    -v, --verbose
+            Verbose output
+
+    -V, --version
+            Print version information
+
+    -z, --optimize
+            Optimize compilation [WIP]
+
 ```
 
 _NOTE: To generate the above output, run: `huffc --help`_
 
-
 ## Usage
 
 To run `huffc` from the command line, you can simply run:
+
 ```bash
 huffc --help
 ```
 
 By default, huffc will attempt to compile all contracts in the `contracts` directory. If there is no `contracts` directory present, the following will spit out an error like so:
+
 ```bash,color=red
 ~ huffc
 
@@ -90,18 +134,19 @@ huffc -o ./artifact.json ./huff-examples/erc20/contracts/ERC20.huff
 ```
 
 **NOTE**: The following will _not_ compile since multiple artifacts cannot be output to the same artifact json file.
+
 ```bash
 huffc -o ./artifact.json ./contracts/
 ```
 
-
 #### Entering Constructor Arguments
 
 `huffc` supports passing in constructor arguments to the contract. This is done by passing in the `--interactive` (shorthand: `-n`) flag or passing the `--inputs` (shorthand: `-i`) flag.
 
- and passing in the arguments as a comma separated list.
+and passing in the arguments as a comma separated list.
 
 For example, to compile a contract (let's call it `example.huff`) with the following constructor definition:
+
 ```huff
 #define macro CONSTRUCTOR(uint256, address) = takes(0) returns (0) {
     0x04 calldataload
@@ -119,14 +164,14 @@ $ huffc -b -n ./contracts/example.huff
 [INTERACTIVE] Enter a uint256 for constructor param: 100
 [INTERACTIVE] Enter a address for constructor param: 0xdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef
 
-33600.....f30000000000000000000000000000000000000000000000000000000000000064000000000000000000000000deadbeefdeadbeefdeadbeefdeadbeefdeadbeef
+335f.....f30000000000000000000000000000000000000000000000000000000000000064000000000000000000000000deadbeefdeadbeefdeadbeefdeadbeefdeadbeef
 ```
 
 Alternatively, you can enter the arguments as a comma separated list by using the `-i` or `--inputs` flag like so:
 
 ```bash
 $ huffc -b -i 100, 0xdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef ./contracts/example.huff
-33600.....f30000000000000000000000000000000000000000000000000000000000000064000000000000000000000000deadbeefdeadbeefdeadbeefdeadbeefdeadbeef
+335f0.....f30000000000000000000000000000000000000000000000000000000000000064000000000000000000000000deadbeefdeadbeefdeadbeefdeadbeefdeadbeef
 ```
 
 #### Other Options
@@ -136,15 +181,16 @@ $ huffc -b -i 100, 0xdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef ./contracts/exampl
 - `-z` or `--optimize`: Optimizes the contract compilation - a work in progress.
 - `-g` or `--interface`: Generates a solidity interface for the contract.
 
-
 ## Building huffc from source
 
 To run `huffc` from the command line, you can use the following command:
+
 ```bash
 cargo run --bin huffc
 ```
 
 To pass arguments into the `huffc` binary, simply pass them in after a `--` flag. For example, to get the `huffc` version (a `-V` flag), you can run:
+
 ```bash
 cargo run --bin huffc -- -V
 ```