enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-12-24 17:01:38 +03:00
Code Issues Projects Releases Wiki Activity
dcba966754
enso/engine
History
Hubert Plociniczak dcba966754
Use a custom directory for VCS repo metadata (#3921) 
Rather than hard-coding `.git` in the root of the project, VCS should save data into Enso's data directory (i.e. `.enso`).
This change reshuffles initialization and configuration to store Git VCS metadata by default at `.enso/.git`.
This is follow up to https://github.com/enso-org/enso/pull/3851

# Important Notes
Apparently a custom Git directory in JGit means that it always creates a `.git` **file** with `gitdir` pointing to the custom location.
This is not necessary in our case since all our commands provide that explicitly.
That is why `init` operation removes `.git` file, which may seem a bit counter-intuitive.
2022-11-29 14:40:36 +00:00
..
language-server Use a custom directory for VCS repo metadata (#3921) 2022-11-29 14:40:36 +00:00
launcher/src Update Scala to 2.13.8 (#3631) 2022-08-08 19:32:55 +00:00
polyglot-api/src Check that type names are resolved (#3895) 2022-11-21 22:33:36 +00:00
runner Upgrade to GraalVM 22.3.0 (#3663) 2022-11-23 14:30:48 +00:00
runtime Better error recovery when body is null (#3925) 2022-11-29 09:55:16 +00:00
runtime-instrument-id-execution/src/main/java/org/enso/interpreter/instrument State rework & IO Contexts (#3828) 2022-10-26 16:22:08 +00:00
runtime-instrument-repl-debugger/src/main/java/org/enso/interpreter/instrument Upgrade to GraalVM 22.3.0 (#3663) 2022-11-23 14:30:48 +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 Upgrade to GraalVM 22.3.0 (#3663) 2022-11-23 14:30:48 +00:00
runtime-with-instruments/src/test Tidy Standard.Base part 4 of n ... (#3898) 2022-11-25 02:00:16 +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.