简体   繁体   English

概括 Int -> Int, Int-> String, String -> String, String -> Int

[英]generalize Int -> Int, Int-> String, String -> String, String -> Int

I have 4 methods with one logic and 4 possible type mapping:我有 4 种方法,一种逻辑和 4 种可能的类型映射:

  def convertStringToString(in: String): String = ???
  def convertIntToString(in: Int): String = ???
  def convertIntToInt(in: Int): Int = ???
  def convertStringToInt(in: String): Int = ???

I want to generalize input and output type and write logic in one methods.我想概括输入和 output 类型并用一种方法编写逻辑。 Tried to generelize input parameter:试图通用化输入参数:

  def convertToInt[IN](in: IN): Int = in match {
    case x: String if x.forall(_.isDigit) => x.toInt
    case y: Int => y
    case _ => 0
  }
  def convertToString[IN](in: IN): String = convertToInt[IN](in).toString

Could you help me to generalize second:你能帮我概括一下吗:

  def convertToInt[IN, OUT](in: IN): OUT = ???

If you really wanted to, you could have something typeclass-based:如果你真的想要,你可以有一些基于类型类的东西:

def convert[I, O](in: I)(implicit c: ConversionRule[I, O]): O = {
  if (c.isConvertible(in)) c.convert(in)
  else c.zero
}

trait ConversionRule[I, O] {
  def isConvertible(in: I): Boolean
  def convert(in: I): O
  def zero: O // Could possibly derive the zero from, e.g., a cats Monoid instance where such exists
}

The eagle-eyed may notice that the isConvertible / convert methods match the contract of PartialFunction[I, O] 's isDefinedAt / apply , so may as well just use PartialFunction (and rewrite convert with isDefinedAt / apply )眼尖的人可能会注意到isConvertible / convert方法与PartialFunction[I, O]isDefinedAt / apply的合同相匹配,所以不妨只使用PartialFunction (并用isDefinedAt / apply重写convert

trait ConversionRule[I, O] extends PartialFunction[I, O] {
  def zero: O
}

zero can be implemented in terms of PartialFunction.applyOrElse , but for the case where zero is constant (which is the case where referential transparency is preserved), this is much faster. zero可以根据PartialFunction.applyOrElse来实现,但是对于zero为常数的情况(即保留引用透明度的情况),这要快得多。

Smart constructors can be defined:可以定义智能构造函数:

object ConversionRule {
  def apply[I, O](zeroValue: O)(pf: PartialFunction[I, O]): ConversionRule[I, O] =
    new ConversionRule[I, O] {
      override def apply(i: I): O = pf(i)
      override def isDefinedAt(i: I): Boolean = pf.isDefinedAt(i)
      val zero: O = zeroValue
    }

  def totalConversion[I, O](f: I => O): ConversionRule[I, O] =
    new ConversionRule[I, O] {
      override def apply(i: I) = f(i)
      override def isDefinedAt(i: I) = true
      override def zero: O = throw new AssertionError("Should not call since conversion is defined")
    }

  // Might want to put this in a `LowPriorityImplicits` trait which this object extends
  implicit def identityConversion[I]: ConversionRule[I, I] =
    totalConversion(identity)
}

identityConversion means that a convertIntToInt gets automatically generated. identityConversion意味着自动生成一个convertIntToInt

convertStringToInt can then be defined as convertStringToInt然后可以定义为

implicit val stringToIntConversion = ConversionRule[String, Int](0) {
  case x if x.forAll(_.isDigit) => x.toInt
}

One can define a toString based conversion (basically the non-lawful Show proposed for alleycats):可以定义一个基于toString的转换(基本上是为 alleycats 提出的非法Show ):

implicit def genericToString[I]: ConversionRule[I, String] =
  ConversionRule.totalConversionRule(_.toString)

And it should then be possible to define a stringViaInt ConversionRule derivation like:然后应该可以定义一个stringViaInt ConversionRule派生,如:

implicit def stringViaInt[I, O](implicit toInt: ConversionRule[I, Int]): ConversionRule[I, String] =
  convert(convert(in)(toInt))

The only really useful thing this provides is an opt-in to usage of implicit conversions.它提供的唯一真正有用的东西是选择使用隐式转换。 Whether that's enough of a gain to justify?这是否足以证明是合理的? shrug耸耸肩

(Disclaimer: only the scala compiler in my head has attempted to compile this) (免责声明:只有我脑海中的 scala 编译器试图编译这个)

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM