Replace a deprecated kotlinOptions to compilerOptions Extension

[Jaehwa-Noh]

As title, Applying this documentation instruction.
https://kotlinlang.org/docs/gradle-compiler-options.html#example-of-additional-arguments-usage-via-freecompilerargs

import org.jetbrains.kotlin.gradle.tasks.KotlinCompilationTask
// ...

kotlin {
    compilerOptions {
        // Specifies the version of the Kotlin API and the JVM target
        apiVersion.set(KotlinVersion.KOTLIN_2_1)
        jvmTarget.set(JvmTarget.JVM_1_8)

        // Single experimental argument
        freeCompilerArgs.add("-Xexport-kdoc")

        // Single additional argument
        freeCompilerArgs.add("-Xno-param-assertions")

        // List of arguments
        freeCompilerArgs.addAll(
            listOf(
                "-Xno-receiver-assertions",
                "-Xno-call-assertions"
            )
        )
    }
}

[gemini-code-assist]

Summary of Changes

Hello @Jaehwa-Noh, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a crucial maintenance update for the project's Gradle build configurations. It systematically replaces the outdated kotlinOptions block with the recommended kotlin { compilerOptions { ... } } structure across multiple modules. This change is essential for maintaining compatibility with future Kotlin Gradle plugin versions and adhering to current best practices for defining Kotlin compiler settings, such as JVM target and free compiler arguments.

Highlights

• Kotlin Gradle Plugin Configuration Update: Migrated from the deprecated kotlinOptions block to the modern kotlin { compilerOptions { ... } } extension across all affected Gradle build scripts. This aligns with the latest Kotlin Gradle plugin recommendations.
• Standardized Compiler Arguments: Ensured consistent configuration of jvmTarget and freeCompilerArgs (specifically -Xcontext-receivers) using the new compilerOptions syntax in all relevant build.gradle.kts files.
• Copyright Year Update: Updated the copyright year from 2023 to 2025 in benchmark/build.gradle.kts.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly replaces the deprecated kotlinOptions extension with the modern compilerOptions DSL across all relevant Gradle build scripts. The changes are consistent and align with the official Kotlin documentation for Gradle compiler options. The migration to compilerOptions improves the build scripts by using the current, type-safe APIs, for instance by using jvmTarget.set(JvmTarget.JVM_1_8) and freeCompilerArgs.add(...). The changes are well-executed and I have no further suggestions.