https://kotlinlang.org logo
Channels
Powered by
#coroutines
  • u

    uhe

    07/27/2017, 12:26 PM
    Copy code
    for (it in channel) {
    if(it.sth()){
        doSth()
    } else {
        break
  }
}
  • r

    rafal

    07/27/2017, 12:27 PM
    I feel strange repulsion for using 
    for
    in "consumer" code 😛 I prefer lambda-like approach e.g. 
    forEach{}
  • g

    groostav

    07/27/2017, 4:14 PM
    @rafal yeah I recently had this too, the most obvious reason being 
    foreach
    with 
    it
    doesnt require the 
    varName in
    preamble. For some tasks its quite nice
  • g

    groostav

    07/27/2017, 4:14 PM
    You're a monster if your 
    foreach { it
    makes multiple references to 
    it
    or is a multi-liner. Then switch that bad-boy out for a 
    for-loop
    or at least a named argument. but this is really #codingconventions
  • f

    feroz_baig

    07/27/2017, 6:42 PM
    Anything about https://github.com/Kotlin/anko/issues/393 ? Slack Conversation
  • r

    rogeralsing

    07/27/2017, 9:02 PM
    Is there any better way to do this: 
    future { theFuture }.await()
    e.g. if there is some extension that lets me do this out of the box instead of first turning the future into a deferred and then awaiting the deferred
  • k

    kingsley

    07/27/2017, 9:11 PM
    @rogeralsing ^
  • r

    rogeralsing

    07/27/2017, 9:16 PM
    ah, thanks
  • r

    rogeralsing

    07/29/2017, 8:00 PM
    @elizarov have you seen that the Akka team are building a thread affinity pool for their actor scheduling?
  • r

    rogeralsing

    07/29/2017, 8:00 PM
  • r

    rogeralsing

    07/29/2017, 8:01 PM
  • r

    rogeralsing

    07/29/2017, 8:04 PM
    TLDR; they have a pool of fixed threads, each actor is then assigned via hashing to one of those threads
  • e

    elizarov

    07/29/2017, 8:36 PM
    @rogeralsing Thanks for the link. We need something like that, though fixed assignent is a bummer in practice. There need to be a way for actors to hop from overloaded threads to free ones.
  • r

    rogeralsing

    07/29/2017, 8:37 PM
    I know, if one locks up, none of the others on the same can run..
  • e

    elizarov

    07/29/2017, 8:45 PM
    It works really well on micro-benchmarks, though. Beats them all 🙂
  • r

    rogeralsing

    07/29/2017, 9:10 PM
    These are the total times for the hotspots in my benchmarks.
  • u

    user

    07/29/2017, 9:12 PM
    @rogeralsing commented on @rogeralsing’s file

    https://kotlinlang.slack.com/files/U0CG5M9T4/F6ERK19U0/pasted_image_at_2017_07_29_11_09_pm.png▾

    : I'm not so sure the FJP or scheduling is an issue
  • u

    user

    07/29/2017, 9:17 PM
    @rogeralsing commented on @rogeralsing’s file

    https://kotlinlang.slack.com/files/U0CG5M9T4/F6ERK19U0/pasted_image_at_2017_07_29_11_09_pm.png▾

    : @elizarov there is a big step from DefaultMailbox.run and ActorContext.invokeUserMessage there. invokeUserMessage is called repeatedly from run. both are suspend funcs. does this mean there is quite a bit of time lost awaiting the result of the invokeUserMessage?
  • u

    user

    07/29/2017, 9:18 PM
    @rogeralsing commented on @rogeralsing’s file

    https://kotlinlang.slack.com/files/U0CG5M9T4/F6ERK19U0/pasted_image_at_2017_07_29_11_09_pm.png▾

    : run dequeues messages off the actor mailbox, and forwards each message to invokeUserMessage. I'd expect the bars to be almost the same size. minus popping overhead
  • g

    gildor

    08/03/2017, 3:57 PM

    https://youtu.be/3xalVUY69Ok▾

    👍 2
  • e

    elizarov

    08/03/2017, 4:00 PM
    👍 4
  • k

    kirillrakhman

    08/03/2017, 6:02 PM
    very interesting to see the journy recapped
  • k

    kirillrakhman

    08/03/2017, 6:03 PM
    I'm strongly agreeing with the decision to make sequential the default. Your talks come to my mind every time I need to wrtie 
    await
    in C# 😄
  • j

    jw

    08/05/2017, 2:52 AM
    i read somewhere that coroutines were already working for multiplatform but as far as I can tell all the deps are for the JVM
  • e

    elizarov

    08/05/2017, 3:19 AM
    @jw They work at the language level. Libraries are not ported yet.
  • j

    jw

    08/05/2017, 3:22 AM
    sorry so to clarify: the "backend" is there, but the library required to reference the types needed to create them is only available for the JVM?
  • e

    elizarov

    08/05/2017, 3:30 AM
    Not exactly. 
    suspendCoroutine
    and 
    startCoroutine
    are there so you can go and write Promise.await extension and async builder. But you have to write them. There is no 
    launch
    or 
    async
    out of the box.
  • j

    jw

    08/05/2017, 3:32 AM
    got it. but in the future we can expect most of 'core' to move to a common module?
  • e

    elizarov

    08/05/2017, 3:40 AM
    @jw Yes. That is the plan.
  • j

    jw

    08/05/2017, 3:40 AM
    awesome. looking forward to it! especially as i dive into the multiplatform stuff a lot more
1...370371372...571Latest