Skip to content

Commit 0a67182

Browse files
Merge pull request #6686 from yoohaemin/patch-1
Fix typo, reorder words for better clarity
2 parents a1b6bb6 + 414b58e commit 0a67182

File tree

1 file changed

+2
-3
lines changed
  • docs/docs/reference/metaprogramming

1 file changed

+2
-3
lines changed

docs/docs/reference/metaprogramming/toc.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,8 @@ introduce the following fundamental facilities:
1010
a definition will be inlined at the point of use. The primary motivation
1111
behind inline is to reduce the overhead behind function calls and access to
1212
values. The expansion will be performed by the Scala compiler during the
13-
`Typer` compiler phase. Unlike Scala's existsing
14-
As opposed to inline in some other ecosystems,
15-
inlining is not merely a request to the compiler but for Scala it is a
13+
`Typer` compiler phase. As opposed to inlining in some other ecosystems,
14+
inlining in Scala is not merely a request to the compiler but is a
1615
_command_. The reason is that inlining in Scala can drive other compile-time
1716
operations, like inline pattern matching (enabling type-level
1817
programming), macros (enabling compile-time, generative, metaprogramming) and

0 commit comments

Comments
 (0)