Skip to content

Fix typo, reorder words for better clarity #6686

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
Jun 19, 2019
Merged

Fix typo, reorder words for better clarity #6686

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
5 changes: 2 additions & 3 deletions docs/docs/reference/metaprogramming/toc.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,8 @@ introduce the following fundamental facilities:
a definition will be inlined at the point of use. The primary motivation
behind inline is to reduce the overhead behind function calls and access to
values. The expansion will be performed by the Scala compiler during the
`Typer` compiler phase. Unlike Scala's existsing
As opposed to inline in some other ecosystems,
inlining is not merely a request to the compiler but for Scala it is a
`Typer` compiler phase. As opposed to inlining in some other ecosystems,
inlining in Scala is not merely a request to the compiler but is a
_command_. The reason is that inlining in Scala can drive other compile-time
operations, like inline pattern matching (enabling type-level
programming), macros (enabling compile-time, generative, metaprogramming) and
Expand Down