enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-12-20 19:41:50 +03:00
Code Issues Projects Releases Wiki Activity
582a9aaa3d
enso/docs/semantics/README.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

36 lines
1.3 KiB
Markdown
Raw Normal View History

Restructure the developer documentation (#751)
2020-05-15 13:41:26 +03:00
---
layout: section-summary
title: Enso's Semantics
category: semantics
tags: [semantics, readme]
order: 0
---
# Enso's Semantics
Add a markdown style guide (#1022)
2020-07-21 15:59:40 +03:00
Restructure the developer documentation (#751)
2020-05-15 13:41:26 +03:00
Much like we have specifications for the [syntax](../syntax/README.md) and the
[type system](../types/README.md) in Enso, we also need a specification of the
Add a markdown style guide (#1022)
2020-07-21 15:59:40 +03:00
language semantics. These documents specify the executable semantics of the Enso
language.
Restructure the developer documentation (#751)
2020-05-15 13:41:26 +03:00
> 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:**](./bindings.md) The semantics of Enso's binding expressions.
- [**Diagnostics:**](./diagnostics.md) The semantics of Enso's executable
compiler diagnostics.
- [**Dispatch:**](./dispatch.md) The semantics of Enso's dispatch system.
- [**Errors:**](./errors.md) The semantics of Enso's various error systems.
Support on_problems=Problem_Behavior.Report_Warning and Map_Error wrapping in Vector.map (#8595) Implements `Warnings.get_all wrap_errors=True` which wraps warnings attached to values inside vectors with `Map_Error`, which includes the position of the value within the vector. See [the documentation](https://github.com/enso-org/enso/blob/develop/docs/semantics/wrapped-errors.md) for more details. `get_all wrap_errors=True` does not change the warnings that are attached to values -- it wraps them before returning them to the caller, but does not change the original warnings attached to the values. Wrapped warnings only appear attached to the vector itself. The values inside the vector do not have their warnings wrapped. Warning propagation is not changed at all; `Warnings.get_all` (with default `wrap_errors=False`) behaves as before. `get_all wrap_errors=True` is meant to be used primarily by the IDE, although it can be used anywhere this wrapping is desired.
2024-01-16 12:36:22 +03:00
- [**Wrapped Errors:**](./wrapped-errors.md) The semantics of Enso's various
error systems.
Add a markdown style guide (#1022)
2020-07-21 15:59:40 +03:00
- [**Evaluation:**](./evaluation.md) Enso's evaluation semantics, including
Restructure the developer documentation (#751)
2020-05-15 13:41:26 +03:00
those of suspended computations.
- [**Modules:**](./modules.md) The semantics of Enso's modules.
- [**Scoping:**](./scoping.md) Enso's scoping and identifier resolution rules.
Implement private modules (#7840) Adds the ability to declare a module as *private*. Modifies the parser to add the `private` keyword as a reserved keyword. All the checks for private modules are implemented as an independent *Compiler pass*. No checks are done at runtime. # Important Notes - Introduces new keyword - `private` - a reserved keyword. - Modules that have `private` keyword as the first statement are declared as *private* (Project private) - Public module cannot have private submodules and vice versa. - This would require runtime access checks - See #7088 for the specification.
2023-10-04 13:33:10 +03:00
- [**Encapsulation:**](./encapsulation.md) The semantics of Enso's encapsulation
system - access restriction.
Reference in New Issue Copy Permalink