enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-11-23 16:18:23 +03:00
Code Issues Projects Releases Wiki Activity
a53fbb6dcc
enso/engine
History
Radosław Waśko a53fbb6dcc
Make REPL display results using to_text (#3411) 
[ci no changelog needed]

# Important Notes
The REPL used to use some builtin Java text representation leading to outputs like this:
```
> [1,2,3]
>>> Vector [1, 2, 3]
> 'a,b,c'.split ','
>>> Vector JavaObject[[Ljava.lang.String;@131c0b6f (java.lang.String[])]
```

This PR makes it use `to_text` (if available, otherwise falling back to regular `toString`). This way we get outputs like this:

```
> [1,2,3]
>>> [1, 2, 3]
> 'a,b,c'.split ','
>>> ['a', 'b', 'c']
```
2022-04-21 14:13:45 +00:00
..
language-server Apply automatic formatting prior to turning on checks (#3405) 2022-04-19 12:34:34 +02:00
launcher/src Data analysts should be able to use Text.location_of to find indexes within string using various matchers (#3324) 2022-03-12 19:42:00 +00:00
polyglot-api/src Apply automatic formatting prior to turning on checks (#3405) 2022-04-19 12:34:34 +02:00
runner Implement the component resolving algorithm (#3244) 2022-02-03 10:40:39 +03:00
runtime Make REPL display results using to_text (#3411) 2022-04-21 14:13:45 +00:00
README.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00

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.