Skip to content

Mention library version quirk #2329

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Feb 23, 2022
Merged

Mention library version quirk #2329

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
19 changes: 16 additions & 3 deletions _overviews/FAQ/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,9 +105,22 @@ get poor results, try surrounding the symbol with double quotes.
sbt 1.x always uses Scala 2.12 to compile build definitions.
Your sbt 1.x build definition is always a Scala 2.12 program.

Regardless, in your `build.sbt` you can set `scalaVersion` to anything
you want and your actual program code will be compiled with that
version.
Regardless, in your `build.sbt`, you can set `scalaVersion` to whichever
available distribution you want and your program code will be compiled with that version.

### I want Scala 3.1.1 (etc); why does std lib say it's using Scala 2.13?

Scala 3 currently uses the Scala 2.13 library by leveraging its seamless
interoperability. Note that it does not necessarily ingest the latest
version of the Scala 2.13 library.

```
Welcome to Scala 3.1.1 (17.0.2, Java OpenJDK 64-Bit Server VM).
Type in expressions for evaluation. Or try :help.

scala> util.Properties.versionString
val res0: String = version 2.13.6
```

### Why is my (abstract or overridden) `val` null?

Expand Down