Skip to content

Mention implicit conversion restrictions in overview #4354

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 2 commits into from
Apr 20, 2018
Merged

Mention implicit conversion restrictions in overview #4354

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1909201
Mention implicit conversion restrictions in overview
odersky Apr 20, 2018
8c96826
Fix typo
odersky Apr 20, 2018
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
8 changes: 8 additions & 0 deletions docs/docs/reference/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,14 @@ Listed in this section are new language constructs that help precise, typechecke
So what should conceptually be a type error would not be reported and
runtime behavior might change instead. Multiversal equality closes that loophole.

- Restrict Implicit Conversions

([Pending](https://github.com/lampepfl/dotty/pull/4229))
Implicit conversions are very easily mis-used, which makes them the cause of much suprising behavior.
We now require a language feature import not only when an implicit conversion is defined
but also when it is applied. This protects users of libraries that define implicit conversions
from being bitten by unanticipated feature interactions.

- Null safety

(Planned) Adding a `null` value to every type has been called a "Billion Dollar Mistake"
Expand Down