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
8fa8d12cc3
enso/engine
History
Hubert Plociniczak 0e5df935d3
Don't rename imported Main module that only imports names (#3710) 
Turns that if you import a two-part import we had special code that would a) add Main submodule b) add an explicit rename.

b) is problematic because sometimes we only want to import specific names.
E.g.,
```
from Bar.Foo import Bar, Baz
```
would be translated to
```
from Bar.Foo.Main as Foo import Bar, Baz
```
and it should only be translated to
```
from Bar.Foo.Main import Bar, Baz
```

This change detects this scenario and does not add renames in that case.

Fixes [183276486](https://www.pivotaltracker.com/story/show/183276486).
2022-09-16 13:01:06 +00:00
..
language-server create inmem database (#3690) 2022-09-07 12:59:18 +03:00
launcher/src Update Scala to 2.13.8 (#3631) 2022-08-08 19:32:55 +00:00
polyglot-api/src IDE uses new visualization API (#3661) 2022-09-01 15:33:46 +03:00
runner Print result of main (if not Nothing) (#3696) 2022-09-12 15:37:46 +00:00
runtime Don't rename imported Main module that only imports names (#3710) 2022-09-16 13:01:06 +00:00
runtime-instrument-id-execution/src/main/java/org/enso/interpreter/instrument Enable caching in visualization functions (#3618) 2022-08-10 12:01:33 +00:00
runtime-instrument-repl-debugger/src/main/java/org/enso/interpreter/instrument Get rid of free-floating atoms. Everything has a type now! (#3671) 2022-08-30 22:54:53 +00: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 Improved Vector/Array interop (#3667) 2022-09-13 03:07:17 +00:00
runtime-with-instruments/src/test Minor cleanups in tests (#3697) 2022-09-15 14:13:40 +02: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.