}
}

@RequiresOptIn("Analysis should not be allowed to be run from the EDT, as otherwise it may cause IDE freezes.")
public annotation class KaAllowAnalysisOnEdt

/**
 * Allows [analyze][org.jetbrains.kotlin.analysis.api.analyze] to be called on the EDT in the given [action], which is normally not allowed.
 *
 * Analysis is not supposed to be invoked from the EDT, as it may cause freezes. Use at your own risk!
 */
@KaAllowAnalysisOnEdt

    }

    override fun getRejectionReason(): String {
        val application = ApplicationManager.getApplication()

        if (isProhibitedEdtAnalysis(application)) {
            return "Called in the EDT thread."
        }

        if (isProhibitedWriteActionAnalysis(application)) {
            return "Called from a write action."
        }

        permissionRegistry.explicitAnalysisRestriction?.let { restriction ->

import org.jetbrains.kotlin.analysis.api.platform.KotlinOptionalPlatformComponent

/**
 * [KotlinAnalysisPermissionOptions] gives an Analysis API platform the choice whether to allow analysis on the EDT and in write actions by
 * default.
 *
 * @see KotlinDefaultAnalysisPermissionOptions
 */
public interface KotlinAnalysisPermissionOptions : KotlinOptionalPlatformComponent {
    /**

        // Various parts of the IJ plugin use the read/write access checker without being aware that it uses `analyze` under the hood. For
        // now, it makes more sense to allow analysis on EDT/from write actions here, as there are many such usages in the IJ plugin.
        return allowAnalysisOnEdt {
            allowAnalysisFromWriteAction {
                val resolvedCall = analyze(assignment) {