Skip to content

Fix numbering conflict in methods-main-methods.md. #2991

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
Mar 4, 2024
Merged

Fix numbering conflict in methods-main-methods.md. #2991

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
6 changes: 3 additions & 3 deletions _overviews/scala3-book/methods-main-methods.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,8 +123,8 @@ The Scala compiler generates a program from an `@main` method `f` as follows:

For instance, the `happyBirthday` method above generates additional code equivalent to the following class:

{% tabs method_3 %}
{% tab 'Scala 3 Only' for=method_3 %}
{% tabs method_4 %}
{% tab 'Scala 3 Only' for=method_4 %}

```scala
final class happyBirthday {
Expand Down Expand Up @@ -158,7 +158,7 @@ The previous functionality of `App`, which relied on the “magic” `DelayedIni

If programs need to cross-build between Scala 2 and Scala 3, it’s recommended to use an `object` with an explicit `main` method and a single `Array[String]` argument instead:

{% tabs method_4 %}
{% tabs method_5 %}
{% tab 'Scala 2 and 3' %}

```scala
Expand Down