Update docs and yaml fiels

Author: SupunS

.github/workflows/benchmark.yml

@@ -48,15 +48,15 @@ jobs:
 
       - name: Run benchmark on current branch
         run: |
-          ( for i in {1..${{ steps.settings.outputs.benchmark_repetitions }}}; do go test ./... -run=XXX -bench=. -benchmem -shuffle=on; done | sed 's/pkg:.*/pkg: github.com\/onflow\/cadence\/runtime/' ) | tee new.txt
+          ( for i in {1..${{ steps.settings.outputs.benchmark_repetitions }}}; do go test ./... -run=XXX -bench=. -benchmem -shuffle=on; done | sed 's/pkg:.*/pkg: github.com\/onflow\/cadence\/' ) | tee new.txt
       # the package replace line above is to make the results table more readable, since it is not fragmented by package
 
       - name: Checkout base branch
         run: git checkout ${{ github.event.pull_request.base.sha }}
 
       - name: Run benchmark on base branch
         run: |
-          ( for i in {1..${{ steps.settings.outputs.benchmark_repetitions }}}; do go test ./... -run=XXX -bench=. -benchmem -shuffle=on; done | sed 's/pkg:.*/pkg: github.com\/onflow\/cadence\/runtime/' ) | tee old.txt
+          ( for i in {1..${{ steps.settings.outputs.benchmark_repetitions }}}; do go test ./... -run=XXX -bench=. -benchmem -shuffle=on; done | sed 's/pkg:.*/pkg: github.com\/onflow\/cadence\/' ) | tee old.txt
 
       # see https://trstringer.com/github-actions-multiline-strings/ to see why this part is complex
       - name: Use benchstat for comparison

.github/workflows/ci.yml

@@ -49,7 +49,7 @@ jobs:
         run: make ci
 
       - name: Cadence Testing Framework
-        run: cd runtime/stdlib/contracts && flow test --cover --covercode="contracts" crypto_test.cdc
+        run: cd stdlib/contracts && flow test --cover --covercode="contracts" crypto_test.cdc
 
       - name: Upload coverage report
         uses: codecov/codecov-action@v2

.gitignore

@@ -34,10 +34,10 @@ suppressions
 
 coverage.txt
 coverage.txt-e
-runtime/cmd/check/check
-runtime/cmd/main/main
-runtime/cmd/parse/parse
-runtime/cmd/parse/parse.wasm
+cmd/check/check
+cmd/main/main
+cmd/parse/parse
+cmd/parse/parse.wasm
 tools/golangci-lint/golangci-lint
 tools/maprange/maprange
 tools/unkeyed/unkeyed

docs/FAQ.md

@@ -43,7 +43,7 @@ There are several options to run the analyzer pass with the linter tool:
 
 ## Analyzing Cadence values / state snapshots
 
-To analyze Cadence values (`interpreter.Value`), you can use the function [`interpreter.InspectValue`](https://github.com/onflow/cadence/blob/master/runtime/interpreter/inspect.go#L31).
+To analyze Cadence values (`interpreter.Value`), you can use the function [`interpreter.InspectValue`](https://github.com/onflow/cadence/blob/master/interpreter/inspect.go#L31).
 
 To find static types in Cadence values (e.g. in type values, containers, capabilities), you can see which values contain static types in the [Cadence 1.0 static type migration code](https://github.com/onflow/cadence/blob/master/migrations/statictypes/statictype_migration.go#L67).
 

docs/development.md

@@ -2,17 +2,17 @@
 
 ## Tools
 
-The [`runtime/cmd` directory](https://github.com/onflow/cadence/tree/master/runtime/cmd)
+The [`cmd` directory](https://github.com/onflow/cadence/tree/master/cmd)
 contains command-line tools that are useful when working on the implementation for Cadence, or with Cadence code:
 
-- The [`parse`](https://github.com/onflow/cadence/tree/master/runtime/cmd/parse) tool
+- The [`parse`](https://github.com/onflow/cadence/tree/master/cmd/parse) tool
   can be used to parse (syntactically analyze) Cadence code.
   By default, it reports syntactical errors in the given Cadence program, if any, in a human-readable format.
   By providing the `-json` it returns the AST of the program in JSON format if the given program is syntactically valid,
   or syntactical errors in JSON format (including position information).
 
   ```
-  $ echo "X" |  go run ./runtime/cmd/parse
+  $ echo "X" |  go run ./cmd/parse
   error: unexpected token: identifier
    --> :1:0
     |
@@ -21,7 +21,7 @@ contains command-line tools that are useful when working on the implementation f
   ```
 
   ```
-  $ echo "let x = 1" |  go run ./runtime/cmd/parse -json
+  $ echo "let x = 1" |  go run ./cmd/parse -json
   [
     {
       "program": {
@@ -42,28 +42,28 @@ contains command-line tools that are useful when working on the implementation f
             [...]
   ```
 
-- The [`check`](https://github.com/onflow/cadence/tree/master/runtime/cmd/check) tool
+- The [`check`](https://github.com/onflow/cadence/tree/master/cmd/check) tool
   can be used to check (semantically analyze) Cadence code.
   By default, it reports semantic errors in the given Cadence program, if any, in a human-readable format.
   By providing the `-json` it returns the AST in JSON format, or semantic errors in JSON format (including position information).
 
   ```
-  $ echo "let x = 1" |  go run ./runtime/cmd/check                                                                                                                                                                                        1 ↵
+  $ echo "let x = 1" |  go run ./cmd/check                                                                                                                                                                                        1 ↵
   error: error: missing access modifier for constant
    --> :1:0
     |
   1 | let x = 1
     | ^
   ```
 
-- The [`main`](https://github.com/onflow/cadence/tree/master/runtime/cmd/check) tools
+- The [`main`](https://github.com/onflow/cadence/tree/master/cmd/check) tools
   can be used to execute Cadence programs.
   If a no argument is provided, the REPL (Read-Eval-Print-Loop) is started.
   If an argument is provided, the Cadence program at the given path is executed.
   The program must have a function named `main` which has no parameters and no return type.
 
   ```
-   $ go run ./runtime/cmd/main                                                                                                                                                                                                           130 ↵
+   $ go run ./cmd/main                                                                                                                                                                                                           130 ↵
    Welcome to Cadence v0.12.3!
    Type '.help' for assistance.
 
@@ -74,7 +74,7 @@ contains command-line tools that are useful when working on the implementation f
 
    ```
    $ echo 'pub fun main () { log("Hello, world!") }' > hello.cdc
-   $ go run ./runtime/cmd/main hello.cdc
+   $ go run ./cmd/main hello.cdc
    "Hello, world!"
    ```
 
@@ -83,7 +83,7 @@ contains command-line tools that are useful when working on the implementation f
 Run the checker tests with the `cadence.checkConcurrently` flag, e.g.
 
 ```shell
-go test -race -v ./runtime/tests/checker -cadence.checkConcurrently=10
+go test -race -v ./tests/checker -cadence.checkConcurrently=10
 ```
 
 This runs each check of a checker test 10 times, concurrently,

npm-packages/cadence-parser/package.json

@@ -18,7 +18,7 @@
     }
   },
   "scripts": {
-    "build": "npm run build:types && npm run build:esm && npm run build:cjs && GOARCH=wasm GOOS=js go build -o ./dist/cadence-parser.wasm ../../runtime/cmd/parse",
+    "build": "npm run build:types && npm run build:esm && npm run build:cjs && GOARCH=wasm GOOS=js go build -o ./dist/cadence-parser.wasm ../../cmd/parse",
     "build:types": "tsc --emitDeclarationOnly --module system --outDir dist/types",
     "build:esm": "esbuild src/index.ts --bundle --sourcemap --format=esm --outfile=dist/esm/index.mjs",
     "build:cjs": "tsc --module commonjs --target es6 --outDir dist/cjs --declaration false",

tools/compare-parsing/main.go

@@ -19,7 +19,7 @@
 package main
 
 // Parses all programs in a CSV file with header location,code
-// using am old and new runtime/cmd/parse program.
+// using am old and new `cmd/parse` program.
 //
 // It reports already broken programs, programs that are broken with the new parser,
 // and when parses of the old and new parser differ