Skip to content

fix typo #2118

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 3 commits into from
Jul 12, 2021
Merged

fix typo #2118

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
035bd4b
fix typo
performantdata Jul 10, 2021
f0fb8ba
replace British spelling
performantdata Jul 10, 2021
2cc0864
replace possessive with plural
performantdata Jul 10, 2021
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
6 changes: 3 additions & 3 deletions _sips/sips/2014-06-27-42.type.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ many important Scala libraries. The lack of first class syntax for literal types
authors to use the experimental Scala macro system to provide a means to express them. Whilst this
has proved to be extremely successful, it has poor ergonomics (although this can typically be hidden
from library _users_) and is not portable -- because Scala macros in general and the mechanisms used
to expose literal types to Scala programmes in particular depend on internal implementation details
to expose literal types to Scala programs in particular depend on internal implementation details
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unsure if there's a standard here…

of the current Scala compiler.

The poor ergonomics of macro-based exposure of literal types was the original motivation for this
Expand Down Expand Up @@ -207,7 +207,7 @@ val book: Book =

shapeless enables generic programming and type class derivation by providing a mechanism for mapping
a value of a standard Scala algebraic data type onto a sum of products representation type,
essentially nested labelled `Either`'s of the records discussed above. Techniques of this sort are
essentially nested labelled `Either`s of the records discussed above. Techniques of this sort are
widely used, and removing the incidental complexity that comes with encoding via macros will improve
the experience for many users across a wide variety of domains.

Expand Down Expand Up @@ -448,7 +448,7 @@ applications which work with large datasets.
```
final val narrow = 23 // inferred type of narrow: 23

class Widen
class Wide
object Narrow extends Wide
def id[T](t: T): T = t
id(Narrow) // result is Narrow: Narrow.type
Expand Down