enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-11-24 08:41:40 +03:00
Code Issues Projects Releases Wiki Activity
d463a43633
enso/engine
History
Hubert Plociniczak d463a43633
Resolve fully qualified names (#4056) 
Added a separate pass, `FullyQualifiedNames`, that partially resolves fully qualified names. The pass only resolves the library part of the name and replaces it with a reference to the `Main` module.

There are 2 scenarios that could be potentially:
1) the code uses a fully qualified name to a component that has been
parsed/compiled
2) the code uses a fully qualified name to a component that has **not** be
imported

For the former case, it is sufficient to just check `PackageRepository` for the presence of the library name.
In the latter we have to ensure that the library has been already parsed and all its imports are resolved. That would require the reference to `Compiler` in the `FullyQualifiedNames` pass, which could then trigger a full compilation for missing library. Since it has some undesired consequences (tracking of dependencies becomes rather complex) we decided to exclude that scenario until it is really needed.

# Important Notes
With this change, one can use a fully qualified name directly.
e.g.
```
import Standard.Base
main =
Standard.Base.IO.println "Hello world!"
```
2023-01-18 20:19:36 +00:00
..
language-server Allow attaching visualizations to non-existent expressions (#4064) 2023-01-18 18:56:32 +00:00
launcher/src Update Scala to 2.13.8 (#3631) 2022-08-08 19:32:55 +00:00
polyglot-api/src Allow attaching visualizations to non-existent expressions (#4064) 2023-01-18 18:56:32 +00:00
runner Fail runner when update manifest fails (#3990) 2022-12-15 16:12:09 +00:00
runtime Resolve fully qualified names (#4056) 2023-01-18 20:19:36 +00:00
runtime-instrument-id-execution/src/main/java/org/enso/interpreter/instrument Add Polyglot Support in Runtime Tests (#4016) 2023-01-03 14:36:26 +00:00
runtime-instrument-repl-debugger/src/main/java/org/enso/interpreter/instrument Improve undefined method error message on builtin types (#3907) 2022-11-30 13:37:17 +01:00
runtime-instrument-runtime-server/src/main/java/org/enso/interpreter/instrument Register instruments/language in their own compilation units to fix the sbt build issues (#3509) 2022-06-13 14:09:08 +00:00
runtime-language-epb/src/main/java/org/enso/interpreter/epb Simplify exception handling for polyglot exceptions (#3981) 2022-12-19 19:16:43 +00:00
runtime-with-instruments/src/test Fix clearing modules' sources during fileClose (#4059) 2023-01-18 17:48:51 +00:00
runtime-with-polyglot/src/test Allow attaching visualizations to non-existent expressions (#4064) 2023-01-18 18:56:32 +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.