mirror of https://github.com/enso-org/enso.git synced 2024-11-27 18:12:31 +03:00

History

Hubert Plociniczak fba5047acc Improved Vector/Array interop (#3667 ) `Vector` type is now a builtin type. This requires a bunch of additional builtin methods for its creation: - Use `Vector.from_array` to convert any array-like structure into a `Vector` [by copy](`f628b28f5f`) - Use (already existing) `Vector.from_polyglot_array` to convert any array-like structure into a `Vector` without copying - Use (already existing) `Vector.fill 1 item` to create a singleton `Vector` Additional, for pattern matching purposes, we had to implement a `VectorBranchNode`. Use following to match on `x` being an instance of `Vector` type: ``` import Standard.Base.Data.Vector size = case x of Vector.Vector -> x.length _ -> 0 ``` Finally, `VectorLiterals` pass that transforms `[1,2,3]` to (roughly) ``` a1 = 1 a2 = 2 a3 = 3 Vector (Array (a1,a2, a3)) ``` had to be modified to generate ``` a1 = 1 a2 = 2 a3 = 3 Vector.from_array (Array (a1, a2, a3)) ``` instead to accomodate to the API changes. As of `025acaa676` all the known CI checks passes. Let's start the review. # Important Notes Matching in `case` statement is currently done via `Vector_Data`. Use: ``` case x of Vector.Vector_Data -> True ``` until a better alternative is found.	2022-09-13 03:07:17 +00:00
..
src	Improved Vector/Array interop (#3667 )	2022-09-13 03:07:17 +00:00
README.md	Add a markdown style guide (#1022 )	2020-07-21 13:59:40 +01:00

Hubert Plociniczak fba5047acc

`Vector` type is now a builtin type. This requires a bunch of additional builtin methods for its creation:
- Use `Vector.from_array` to convert any array-like structure into a `Vector` [by copy](f628b28f5f)
- Use (already existing) `Vector.from_polyglot_array` to convert any array-like structure into a `Vector` **without** copying
- Use (already existing) `Vector.fill 1 item` to create a singleton `Vector`

Additional, for pattern matching purposes, we had to implement a `VectorBranchNode`. Use following to match on `x` being an instance of `Vector` type:
```
import Standard.Base.Data.Vector

size = case x of
Vector.Vector -> x.length
_ -> 0
```

Finally, `VectorLiterals` pass that transforms `[1,2,3]` to (roughly)
```
a1 = 1
a2 = 2
a3 = 3
Vector (Array (a1,a2, a3))
```
had to be modified to generate
```
a1 = 1
a2 = 2
a3 = 3
Vector.from_array (Array (a1, a2, a3))
```
instead to accomodate to the API changes. As of 025acaa676 all the known CI checks passes. Let's start the review.

# Important Notes
Matching in `case` statement is currently done via `Vector_Data`. Use:
```
case x of
Vector.Vector_Data -> True
```
until a better alternative is found.

2022-09-13 03:07:17 +00:00

src Improved Vector/Array interop (#3667 ) 2022-09-13 03:07:17 +00:00

README.md Add a markdown style guide (#1022 ) 2020-07-21 13:59:40 +01:00

README.md

Enso Runtime

The Enso runtime is responsible for the actual execution of Enso code. This means that it encompasses the following functionality:

Parsing: Taking Enso code as input and generating an AST that maintains a sophisticated set of information about the input.
Desugaring: Reducing the user-facing Enso code into a simplified language known as Core.
Type Inference: Inferring the types of bindings in the user's code.
Type Checking: Checking that the inferred and provided types for bindings match up across the codebase.
Optimisation: Static optimisation processes to improve the performance of the user's program.
Code Execution: Actually running the Enso code.
Introspection Hooks: Providing hooks into the running code to allow the language server to inspect information about the code as it runs.

Truffle Nodes creation convention

All Truffle nodes that are expected to be created as part of ASTs should implement a public, static build method for creating an instance. If the node is DSL generated, the build method should delegate to the autogenerated create method, so that nodes are always created with build. Such a convention allows us to easily switch node back and forth between manual and DSL generated implementations, without the need to change its clients.

The only exception are nodes that are never expected to be a part of an AST – e.g. root nodes of builtin functions, for which an asFunction method should be implemented instead.

This convention should be implemented for every node throughout this codebase – if you see one not obeying it – please fix it.

README.md Unescape Escape

Enso Runtime

Truffle Nodes creation convention

README.md