mirror of
https://github.com/enso-org/enso.git
synced 2024-11-24 08:41:40 +03:00
12d6ef799f
Promoted `with`, `take`, `finalize` to be methods of Managed_Resource rather than static methods always taking `resource`, for consistency reasons. This required function dispatch boilerplate, similarly to `Ref`. In future iterations we will address this boilerplate code. Related to https://www.pivotaltracker.com/story/show/182212217 |
||
---|---|---|
.. | ||
bindings.md | ||
diagnostics.md | ||
dispatch.md | ||
errors.md | ||
evaluation.md | ||
managed-resources.md | ||
modules.md | ||
numbers.md | ||
README.md | ||
scoping.md | ||
tail-call-optimization.md |
layout | title | category | tags | order | ||
---|---|---|---|---|---|---|
section-summary | Enso's Semantics | semantics |
|
0 |
Enso's Semantics
Much like we have specifications for the syntax and the type system in Enso, we also need a specification of the language semantics. These documents specify the executable semantics of the Enso language.
The actionables for this section are:
- As we make more semantic determinations about the language these should be written down here.
This specification is broken down into the following sections:
- Bindings: The semantics of Enso's binding expressions.
- Diagnostics: The semantics of Enso's executable compiler diagnostics.
- Dispatch: The semantics of Enso's dispatch system.
- Errors: The semantics of Enso's various error systems.
- Evaluation: Enso's evaluation semantics, including those of suspended computations.
- Modules: The semantics of Enso's modules.
- Scoping: Enso's scoping and identifier resolution rules.