Kotlin Result类在Guice构造注入中失效的原因及解决方法

当使用Kotlin的Result作为泛型参数配置Guice绑定后，构造注入时抛出MissingImplementation异常，但手动通过injector.getInstance()可以正常获取实例。其他泛型类型（如Java Optional或自定义泛型类）则无此问题。使用版本：Kotlin 1.7.10，Guice 5.1.0。

绑定配置 #

import com.google.inject.AbstractModule
import com.google.inject.Singleton
import com.google.inject.TypeLiteral

class BillingModule : AbstractModule() {
    override fun configure() {
        bind(object : TypeLiteral<CardProcessor<Result<String>>>() {})
            .toProvider(CreditCardProcessorProvider::class.java)
            .`in`(Singleton::class.java)

        bind(object : TypeLiteral<CardProcessor<Result<Int>>>() {})
            .toProvider(DebitCardProcessorProvider::class.java)
            .`in`(Singleton::class.java)
    }
}

Guice Provider实现 #

CreditCardProcessorProvider #

import com.google.inject.Provider

class CreditCardProcessorProvider : Provider<CardProcessor<Result<String>>> {
    private val creditCardProcessor = CreditCardProcessor<Result<String>>()
    override fun get(): CardProcessor<Result<String>> {
        return creditCardProcessor
    }
}

DebitCardProcessorProvider #

import com.google.inject.Provider

class DebitCardProcessorProvider : Provider<CardProcessor<Result<Int>>> {
    private val debitCardProcessor = DebitCardProcessor<Result<Int>>()
    override fun get(): CardProcessor<Result<Int>> {
        return debitCardProcessor
    }
}

构造注入的服务类 #

import javax.inject.Inject

class RealBillingService @Inject constructor(
    private val creditCardProcessor: CardProcessor<Result<String>>,
    private val debitCardProcessor: CardProcessor<Result<Int>>,
) {
    fun chargeOrder() {
        val creditCardOutput = creditCardProcessor.charge(Result.success("ok"))
        val debitCardOutput = debitCardProcessor.charge(Result.success(1))
    }
}

抛出的异常信息 #

1) [Guice/MissingImplementation]: No implementation for CardProcessor<kotlin.Result<Integer>> was bound.

Requested by:
1  : RealBillingService.<init>(RealBillingService.kt:3)
      \_ for 2nd parameter
     while locating RealBillingService

2) [Guice/MissingImplementation]: No implementation for CardProcessor<kotlin.Result<String>> was bound.

Requested by:
1  : RealBillingService.<init>(RealBillingService.kt:3)
      \_ for 1st parameter
     while locating RealBillingService

问题原因 #

Kotlin的Result是inline value class，在JVM编译时会被特殊处理：它的泛型参数在运行时的类型表示与普通类存在差异，导致Guice的类型匹配机制无法正确识别Result<String>/Result<Int>和构造参数中反射解析出的类型（如Result<Integer>）的对应关系，最终触发绑定缺失异常。而手动调用getInstance时，我们显式传入了正确的TypeLiteral，绕开了反射解析的类型不匹配问题。

解决方案 #

方案一：用非value class包装Result #

创建普通的data class包装Result，让Guice可以正常识别泛型参数，这是最推荐的方案：

1. 定义包装类

data class ResultWrapper<T>(val value: Result<T>)

2. 修改绑定配置

class BillingModule : AbstractModule() {
    override fun configure() {
        bind(object : TypeLiteral<CardProcessor<ResultWrapper<String>>>() {})
            .toProvider(CreditCardProcessorProvider::class.java)
            .`in`(Singleton::class.java)

        bind(object : TypeLiteral<CardProcessor<ResultWrapper<Int>>>() {})
            .toProvider(DebitCardProcessorProvider::class.java)
            .`in`(Singleton::class.java)
    }
}

3. 更新Provider实现

// CreditCardProcessorProvider
class CreditCardProcessorProvider : Provider<CardProcessor<ResultWrapper<String>>> {
    private val creditCardProcessor = CreditCardProcessor<ResultWrapper<String>>()
    override fun get(): CardProcessor<ResultWrapper<String>> = creditCardProcessor
}

// DebitCardProcessorProvider
class DebitCardProcessorProvider : Provider<CardProcessor<ResultWrapper<Int>>> {
    private val debitCardProcessor = DebitCardProcessor<ResultWrapper<Int>>()
    override fun get(): CardProcessor<ResultWrapper<Int>> = debitCardProcessor
}

4. 修改服务类的注入和调用

class RealBillingService @Inject constructor(
    private val creditCardProcessor: CardProcessor<ResultWrapper<String>>,
    private val debitCardProcessor: CardProcessor<ResultWrapper<Int>>,
) {
    fun chargeOrder() {
        val creditCardOutput = creditCardProcessor.charge(ResultWrapper(Result.success("ok")))
        val debitCardOutput = debitCardProcessor.charge(ResultWrapper(Result.success(1)))
    }
}

方案二：显式指定JVM层面的泛型类型 #

如果不想引入包装类，可以在绑定和构造注入时显式使用Java装箱类型，确保Guice解析的类型完全一致：

修改绑定配置

import java.lang.Integer

class BillingModule : AbstractModule() {
    override fun configure() {
        bind(object : TypeLiteral<CardProcessor<Result<String>>>() {})
            .toProvider(CreditCardProcessorProvider::class.java)
            .`in`(Singleton::class.java)

        bind(object : TypeLiteral<CardProcessor<Result<Integer>>>() {})
            .toProvider(DebitCardProcessorProvider::class.java)
            .`in`(Singleton::class.java)
    }
}

修改服务类的构造参数

import java.lang.Integer

class RealBillingService @Inject constructor(
    private val creditCardProcessor: CardProcessor<Result<String>>,
    private val debitCardProcessor: CardProcessor<Result<Integer>>,
) {
    fun chargeOrder() {
        val creditCardOutput = creditCardProcessor.charge(Result.success("ok"))
        val debitCardOutput = debitCardProcessor.charge(Result.success(1 as Integer))
    }
}

注意：该方案需要混用Kotlin和Java类型，可能降低代码可读性，仅作为备选方案。

内容的提问来源于stack exchange，提问作者Damian