Skip to content

Fix #7881: fix example and add link to -Ycheck-init #8481

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
nicolasstucki merged 1 commit into from
Mar 9, 2020
Merged

Fix #7881: fix example and add link to -Ycheck-init #8481

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
7 changes: 3 additions & 4 deletions docs/docs/reference/other-new-features/explicit-nulls.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,15 +39,14 @@ The unsoundness happens because uninitialized fields in a class start out as `nu
```scala
class C {
val f: String = foo(f)
def foo(f2: String): String = if (f2 == null) "field is null" else f2
def foo(f2: String): String = f2
}
val c = new C()
// c.f == "field is null"
```

Enforcing sound initialization is a non-goal of this proposal. However, once we have a type
system where nullability is explicit, we can use a sound initialization scheme like the one
proposed by @liufengyun and @biboudis in [https://github.com/lampepfl/dotty/pull/4543](https://github.com/lampepfl/dotty/pull/4543) to eliminate this particular source of unsoundness.
The unsoundness above can be caught by the compiler with the option `-Ycheck-init`.
More details can be found in [safe initialization](./safe-initializaion.md).

## Equality

Expand Down