Skip to content

Fix typos in documentation: reference > changed & dropped features #3676

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
Dec 18, 2017
Merged

Fix typos in documentation: reference > changed & dropped features #3676

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion docs/docs/reference/changed/pattern-matching.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,4 +114,4 @@ object Nat {
// 5 is a natural number
```

In case of ambiguities, *Product Pattern* is preferred over *Name Based Pattern*. This document reflects the state of pattern matching as currently implemented in Dotty. They are plans for further simplification, in particular to factor out *Product Pattern* and *Name Based Pattern* into a single type of extractor.
In case of ambiguities, *Product Pattern* is preferred over *Name Based Pattern*. This document reflects the state of pattern matching as currently implemented in Dotty. There are plans for further simplification, in particular to factor out *Product Pattern* and *Name Based Pattern* into a single type of extractor.
2 changes: 1 addition & 1 deletion docs/docs/reference/changed/structural-types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ title: "Programmatic Structural Types"
Previously, Scala supported structural types by means of
reflection. This is problematic on other platforms, because Scala's
reflection is JVM-based. Consequently, Scala.js and Scala.native don't
support structural types fully. The reflction based implementation is
support structural types fully. The reflection based implementation is
also needlessly restrictive, since it rules out other implementation
schemes. This makes structural types unsuitable for e.g. modelling
rows in a database, for which they would otherwise seem to be an ideal
Expand Down
2 changes: 1 addition & 1 deletion docs/docs/reference/dropped/auto-apply.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ requirement.

Existing Scala code with inconsistent parameters can still be compiled
in Dotty under `-language:Scala2`. When paired with the `-rewrite`
option, the code will be automatcally rewritten to conform to Dotty's
option, the code will be automatically rewritten to conform to Dotty's
stricter checking.

### Reference
Expand Down
2 changes: 1 addition & 1 deletion docs/docs/reference/dropped/class-shadowing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Dotty rejects this with the error message:

The issue is that the two `Ops` classes _look_ like one overrides the
other, but classes in Scala cannot be overridden. To keep things clean
(and its internal operations conistent) the Dotty compiler forces you
(and its internal operations consistent) the Dotty compiler forces you
to rename the inner classes so that their names are different.


Expand Down