Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typo fixed in scripts.md #2974

Merged
merged 1 commit into from
Jun 25, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions website/docs/guides/scripting/scripts.md
Original file line number Diff line number Diff line change
Expand Up @@ -287,7 +287,7 @@ The Class Wrapper's behaviour is the default described throughout the documentat

#### Object Wrapper
This wrapper is an alternative to the [Class Wrapper](#class-wrapper) and can be forced with `--object-wrapper` flag and `>// using objectWrapper` directive.
It is used by default for Scala 3 scripts compiled for JS platform. Can suffer from deadlocks then using multithreaded code.
It is used by default for Scala 3 scripts compiled for JS platform. Can suffer from deadlocks when using multithreaded code.

**Limitations**
- When running background threads from the script and using e.g. `scala.concurrent.Await` on them may result in a deadlock due to unfinished initialization of the wrapper object.
Expand Down Expand Up @@ -319,4 +319,4 @@ On the other hand:
- You can pass a single "entry point" script as input to Ammonite, and Ammonite finds the scripts it depends on via
the `import $file` directives
- Scala CLI requires all scripts to be added with `//> using file ...` or to be passed beforehand, either one-by-one, or by putting them in a directory, and
passing the directory to Scala CLI
passing the directory to Scala CLI
Loading