Skip to content
This repository has been archived by the owner on Oct 30, 2023. It is now read-only.

Commit

Permalink
oopsie
Browse files Browse the repository at this point in the history
  • Loading branch information
rawhat committed Oct 29, 2023
1 parent 3b03ae6 commit 00b72f2
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,14 +61,15 @@ Erlang, but there's also the JavaScript target!

Ultimately, all of your Gleam modules can be made available in the Erlang shell
via the `-pa` flag (that the `gleam shell` command already uses). You just
can't write Gleam code. And you can load the standard library in the `node`
shell as well. So realistically this project doesn't provide too much more
can't write Gleam code. And you can load the standard library and your code in
the `node` shell as well. So realistically this project doesn't provide too much more
than you get by default.

## Implementation

The `rappel/shell.{start}` function is the `{module, function, arity}` entrypoint for
`shell:start_interactive/1`. This starts a process which does the following:
The `rappel/shell.{start}` function is the `{module, function, arguments}`
entrypoint for `shell:start_interactive/1`. This starts a process which does
the following:
- generate the temp directory for the shell's Gleam project
- initialize the `Evaluator` process
- initialize the `LSP` process
Expand Down

0 comments on commit 00b72f2

Please sign in to comment.