https://kotlinlang.org logo
Channels
Powered by
#arrow
  • j

    Jacek Modrakowski

    02/11/2018, 8:03 PM
    Error:(13, 39) Kotlin: Unresolved reference: Companion
  • r

    raulraja

    02/11/2018, 8:04 PM
    your data type should include 
    companion object {}
  • r

    raulraja

    02/11/2018, 8:04 PM
    even if empty
  • r

    raulraja

    02/11/2018, 8:05 PM
    Kotlin does not allow extensions in companions unless explicitly declared
  • j

    Jacek Modrakowski

    02/11/2018, 8:06 PM
    Aaaa ok, thats's the trick 😉
  • j

    Jacek Modrakowski

    02/11/2018, 8:06 PM
    So to summarize:
  • j

    Jacek Modrakowski

    02/11/2018, 8:08 PM
    1. There is no special requirements for place where this code should be placed right?
    Copy code
    @instance(User::class)
interface UserEqInstance : Eq<User> {
    override fun eqv(a: User, b: User): Boolean = a == b
}
    2. And model that we've created typeclass for should include empty companion 
    companion object
    to unlock ability for companion's object extensions functions?
  • p

    pakoito

    02/11/2018, 8:10 PM
    yes, because the way of finding/getting the instance becomes an extension function on the companion
  • j

    Jacek Modrakowski

    02/11/2018, 8:11 PM
    So this 
    Companion
    is like a bridge to connect our domain model with typeclass instance generated (UserEqInstanceImplicits.instance()) based on our custom 
    UserEqInstance
    declaration. I'm right?
  • j

    Jacek Modrakowski

    02/11/2018, 8:15 PM
    But btw, thanks for the quick help guys 😉
  • r

    raulraja

    02/11/2018, 8:18 PM
    Yes, this gives you 
    User.eq()
    which points to the instance. Same for other type classes that is why you find 
    Option.monad()
    for example, those are typeclasses as well
  • r

    raulraja

    02/11/2018, 8:19 PM
    We also have a dagger integration we are working on that for dagger users offers compile time resolution of type classes but is not yet documented as it is still fairly experimental
  • r

    raulraja

    02/11/2018, 8:19 PM
  • j

    Jacek Modrakowski

    02/11/2018, 8:58 PM
    Ok I see, dagger support will be very helpfull 😉
  • j

    Jacek Modrakowski

    02/11/2018, 8:59 PM
    And btw, to use power of my UserEq typeclass, I just use it like it right?
    Copy code
    val u1 = User(...)
val u2 = User(...)

val sameUsers = u1.eqv(b = u2)
  • j

    Jacek Modrakowski

    02/11/2018, 9:03 PM
    ot in another way: 
    eq<User>().eqv(u1, u2)
  • s

    simon.vergauwen

    02/11/2018, 9:14 PM
    Yes.
  • j

    Jacek Modrakowski

    02/11/2018, 9:16 PM
    Awesome, thank you very much 🙂 🍻
    🍻 1
  • d

    dcampogiani

    02/11/2018, 9:56 PM
  • r

    raulraja

    02/11/2018, 9:57 PM
    @dcampogiani excellent!
  • d

    dcampogiani

    02/11/2018, 9:57 PM
    Some short posts about validation on Android using arrow
  • d

    dcampogiani

    02/11/2018, 9:58 PM
    Probably with a lot of English mistakes
  • r

    raulraja

    02/11/2018, 9:58 PM
    If you want to submit a PR we can link it in the different datatypes covered
  • r

    raulraja

    02/11/2018, 9:58 PM
  • d

    dcampogiani

    02/11/2018, 9:59 PM
    If you think the content is good enough
  • d

    dcampogiani

    02/11/2018, 9:59 PM
    I can open PR tommorow
  • r

    raulraja

    02/11/2018, 10:00 PM
    definitely, we need simple and clear examples used in the wild for other users
  • j

    jacob

    02/12/2018, 8:54 AM
    has there been a change to the DeferredKW but not yet released?
  • j

    jacob

    02/12/2018, 8:54 AM
    The docs say DeferredK but 0.6.1 only seems to expose DeferredKW. Some of the instance methods seem different as well
  • p

    pguardiola

    02/12/2018, 9:28 AM
    yeah you could try it using the snapshot
1...137138139...416Latest