mirror of
https://github.com/enso-org/enso.git
synced 2025-01-03 21:35:15 +03:00
e5b85bf16e
In a sequence of value-level operators, whitespace does not affect relative precedence. Functional operators still follow the space-precedence rules. The "functional" operators are: `>> << |> |>> <| <<| : .`, application, and any operator containing `<-` or `->`. All other operators are considered value-level operators. Asymmetric whitespace can still be used to form *operator sections* of value-level operators, e.g. `+2 * 3` is still equivalent to `x -> (x+2) * 3`. Precedence of application is unchanged, so `f x+y` is still equivalent to `f (x + y)` and `f x+y * z` is still equivalent to `(f (x + y)) * z`. Any attempt to use spacing to override value-level operator precedence will be caught by the new enso linter. Mixed spacing (for clarity) in value-operator expressions is allowed, as long as it is consistent with the precedences of the operators. Closes #10366. # Important Notes Precedence warnings: - The parser emits a warning if the whitespace in an expression is inconsistent with its effective precedence. - A new enso linter can be run with `./run libraries lint`. It parses all `.enso` files in `distribution/lib` and `test`, and reports any errors or warnings. It can also be run on individual files: `cargo run --release --bin check_syntax -- file1 file2...` (the result may be easier to read than the `./run` output). - The linter is also run as part of `./run lint`, so it is checked in CI. Additional language change: - The exponentiation operator (`^`) now has higher precedence than the multiplication class (`*`, `/`, `%`). This change did not affect any current enso files. Library changes: - The libraries have been updated. The new warnings were used to identify all affected code; the changes themselves have not been programmatically verified (in many cases their equivalence relies on the commutativity of string concatenation). |
||
|---|---|---|
| .. | ||
| common/src/main/java/org/enso/common | ||
| interpreter-dsl-test/src/test/java/org/enso/interpreter/dsl/test | ||
| language-server | ||
| launcher/src | ||
| polyglot-api/src | ||
| polyglot-api-macros/src/main/scala/org/enso/polyglot/macros | ||
| runner | ||
| runner-common/src/main | ||
| runtime | ||
| runtime-benchmarks/src/main | ||
| runtime-compiler/src | ||
| runtime-fat-jar/src/main/java | ||
| runtime-instrument-common/src | ||
| runtime-instrument-id-execution/src/main/java/org/enso/interpreter/instrument | ||
| runtime-instrument-repl-debugger/src/main/java/org/enso/interpreter/instrument | ||
| runtime-instrument-runtime-server/src/main/java/org/enso/interpreter/instrument | ||
| runtime-integration-tests/src/test | ||
| runtime-language-arrow/src | ||
| runtime-language-epb/src | ||
| runtime-parser/src | ||
| runtime-suggestions/src/main/scala/org/enso/compiler/suggestions | ||
| runtime-test-instruments/src/main/java | ||
| README.md | ||
The Enso Engine
The Enso engine is the codebase responsible for compiling and executing Enso code, as well as providing language server functionality to users of the language. It is subdivided into two major components:
- Language Server: The Enso language service.
- Polyglot API: The truffle-boundary safe API for communication between the language server and the runtime.
- Runner: The command-line interface for Enso.
- Runtime: The compiler and interpreter for Enso.