Kotlin / Kotlin/dokka

The CLI runner should use the shadowed stdlib from compiler

Open
#4,331 0 comments 0 reactions 0 assignees View on GitHub
enhancement runner: CLI tech-debt
Dominant language
Kotlin
Stars
3.8k
Forks
500
Avg merge
3d 10h
Merged PRs (30d)
10

Description

The CLI runner uses its own version of stdlib instead of the shadowed stdlib from analysis (see #4178, #4324).

Since the Dokka analysis often uses development versions of the compiler, the standard library (stdlib) of the compiler can be incompatible with the version from the runner.

The ideal solution is to have an isolated classloader like in https://github.com/Kotlin/dokka/pull/4182. Or the CLI runned can be bundled with `symbols-analysis` without the ability to switch between K1 and K2.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the CLI runner and the shadowed stdlib used by analysis, then compare the isolation approach in Dokka PR #4182 and the related issues #4178 and #4324. Determine which proposed approach fits the runner, and verify that development compiler versions no longer conflict with the runner's stdlib.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
cli, compilers
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.