Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Raúl Raja Martínez
    @raulraja
    could theses issue be related to the fact that kinds are now encoded in bow as actual typealiases and not new types?
    Tomás Ruiz-López
    @truizlop
    It looks like that
    Raúl Raja Martínez
    @raulraja
    I noticed too that in SwiftZ they flatten the protocols with associatedtype and they make the extension implement the functions but not the actual protocols themselves. Not sure how they can do ad hoc polymorphism then or if their type classes are just syntax over data types.
    Tomás Ruiz-López
    @truizlop
    I am checking and I have no clue how they can write a polymorphic function based on a typeclass. Also, their definition of Functor, Applicative, etc is similar to Functor3 that I suggested above, but IMO it is wrong since they have both A and B associated with the protocol
    Raúl Raja Martínez
    @raulraja
    right, what they seem to be doing is to apply the parameter to Any in order. So the Bifunctor extensions which does not implement the protocol declare values for A, B etc which they don't have to fill in in other extensions https://github.com/typelift/Swiftz/blob/master/Sources/Swiftz/EitherExt.swift#L14
    And AFAIK that would not allow for abstract functions depending on the evidence of type class instances which is clearly what we want to do here
    Víctor Galán
    @victorg1991
    I have to digest all this stuff, and try some things
    Tomás Ruiz-López
    @truizlop
    I think the way we have implemented things now (with separate instances) is probably the only way of having what we want, although it is a bit difficult to use. We'd need to find a way of providing the instances automatically as you were doing before in Arrow. This will eventually change when Swift supports Higher Kinds natively in the language. Since we've been stuck here for 2-3 weeks, I suggest we continue with the encoding we have for typeclasses right now, complete what's missing in the TO-DO list and publish a first release that we can use to build a few examples and see how easy/difficult is to use.
    Jorge Castillo
    @JorgeCastilloPrz
    Yeah agree
    Tomás Ruiz-López
    @truizlop
    Good morning people! It's been a long time since last time we wrote in this channel, but I'd like to give Bow a boost and try to launch an initial release this week or next at most. In the last few weeks I've been making some contributions to it (currently there are 4 PRs that need approval) and I think the library is in a state where it can be used, maybe not in its full potential, but at least to start receiving feedback and determine how to address usability issues. My intention is to create a few samples like the ones written in Kotlin and see how easy/hard they are to write.
    @victorg1991 could you help me with the publication of the initial release? I've done it some times in Cocoapods, but never used Carthage or SPM, so it would be nice to get your knowledge on this (and perhaps make a script to automate the release process).
    Víctor Galán
    @victorg1991
    Yeah, I can help, let's talk this evening to make the release :)
    Well, if you can ofc, is that ok? @truizlop
    Tomás Ruiz-López
    @truizlop
    sure, we can coordinate
    Tomás Ruiz-López
    @truizlop
    Hi everyone! Last night we published the first version (0.1.0) of Bow! It is now available in Cocoapods, Carthage and the Swift Package Manager. Thanks @victorg1991 for taking care of the release process. This is an initial release so that we can start testing the library with a few projects and examples and find usability problems. Let's spread the word about it!
    Raúl Raja Martínez
    @raulraja
    :clap:
    Tomás Ruiz-López
    @truizlop
    Hi, there has been a conversation in an arrow-kt/bow#44 regarding naming. I originally used Maybe for the option type, since the native version is named Optional, but the guy posting the issue suggests to rename it to Option to match Arrow and other libs conventions. I don't have a clear opinion on this and decided to go for Maybe to make it easily distinguishable from the native one, but I'd like to hear other opinions as well.
    Paco
    @pakoito
    There's also Optional in the Lenses package
    so it'll be hard not to collide
    I'm up for using Option
    Tomás Ruiz-López
    @truizlop
    yes, actually it now collides and users of Bow need to explicitly use Bow.Optional to refer to the optic class
    Raúl Raja Martínez
    @raulraja
    I'm in favor of Option which is used in Scala and Arrow as well
    Jose Luis
    @josete89

    Hi Good morning! I’m just playing around with bow and I have a noob question. I’m trying to writting a simple Yoneda but I ain’t able to do it :(
    Here is my code:

            let maybe = Either<String,Int>.right(2)
            let h = Yoneda.functor(maybe)

    And it’ saying Argument type 'Either<String, Int>' does not conform to expected type 'Functor'

    Jose Luis
    @josete89
    Any advice?
    Paco
    @pakoito
    one sec
    Yoneda.functor(Either.functor())
    try that @josete89
    Jose Luis
    @josete89
    Finally!
    let h = Yoneda<MaybeFunctor.F, Int>.functor(Maybe<Int>.functor())
    this works, thanks a lot @pakoito
    Paco
    @pakoito
    yikes
    that's a lot of hinting
    :D
    Tomás Ruiz-López
    @truizlop
    @raulraja @pakoito or anyone else, I have opened 3 PRs today that I'd need someone to review. They are very short, so I think you can do it quickly, and it would be very nice to have them ready tomorrow to continue building on top of them
    Raúl Raja Martínez
    @raulraja
    :thumbsup:
    Tim
    @tirumalesh123
    How to relate monads in kotlin or java8
    Help please
    Raúl Raja Martínez
    @raulraja
    @tirumalesh123 not sure what you mean by relate but this may get you started https://arrow-kt.io/docs/patterns/monads/
    ask any questions you may have in https://gitter.im/arrow-kt/Lobby
    This channel is for Bow which is Swift specific
    Tim
    @tirumalesh123
    Thanks Raul for your response
    Tomás Ruiz-López
    @truizlop
    Bow 0.2.0 has been released and it is available through CocoaPods and Carthage!
    Raúl Raja Martínez
    @raulraja
    :clap:
    Paco
    @pakoito
    oh wow
    congrats :"D
    Maureen Elsberry
    @MaureenElsberry
    @a
    @all we have a new Gitter for Bow: https://gitter.im/bowswift/bow
    this channel will be closed out in a few days. Thanks!
    Miguel Ángel Díaz
    @miguelangel-dev
    Thanks Maureen ! :)
    Simon Vergauwen
    @nomisRev
    :wave: cya there!
    Raúl Raja Martínez
    @raulraja
    :wave: