Skip to content
This repository

Apr 19, 2014

  1. lizmat

    Add examples for Supply.(merge|zip)

    authored April 19, 2014
  2. lizmat

    Elaborate on Supply.(flat|do|map|grep|uniq|squish)

    authored April 19, 2014

Apr 16, 2014

  1. lizmat

    Elaborate on "on demand" and "live" Supply

    authored April 16, 2014
  2. lizmat

    "is cas" is no more

    authored April 16, 2014

Apr 15, 2014

  1. lizmat

    Amplify the difference between Thread.(start|new)

    Which I completely missed earlier today :-(
    authored April 15, 2014
  2. lizmat

    Thread.new only takes named parameters

    Why make it easier to create threads manually?  We don't really want this to
    be the easiest way to do concurrency in Perl 6.
    authored April 15, 2014
  3. lizmat

    Elaborate on how to give a thread a name

    authored April 15, 2014

Apr 07, 2014

  1. lizmat

    Make winner {} about Channel's only

    authored April 07, 2014
  2. lizmat

    Let's revert back to before I got into this

    authored April 07, 2014

Apr 06, 2014

  1. lizmat

    Clarify that outcome takes Promises* and Channels*

    As in zero or more
    authored April 06, 2014
  2. lizmat

    Remove mention of outcome in Channel spec

    It is mentioned in the "outcome" spec, so premature here.
    authored April 06, 2014
  3. lizmat

    Move introduction of outcome {} after Channel

    The way it was, we're starting to discuss Channels in the context of outcome
    before we specced what a Channel is.
    authored April 06, 2014
  4. lizmat

    Remove Redeemed/.redeem

    authored April 06, 2014

Apr 05, 2014

  1. lizmat

    Spec "outcome/whenever" instead of "winner/done/more"

    For discussion, and for a test implementation.  Please comment / fire on it /
    shoot it down if you think you should.  By no means do I feel this is the
    final thing.  It's just that winner {} currently is *so* broken, we either
    need to fix that, or come up with something else.  This is just my something
    else :-)
    authored April 06, 2014
  2. lizmat

    Add "Redeemed" status and .redeem to Promise

    This would be the equivalent of Channel.close.
    authored April 05, 2014

Apr 04, 2014

  1. lizmat

    Also mention MoarVM

    authored April 04, 2014

Mar 23, 2014

  1. lizmat

    Undraft S17

    authored March 23, 2014

Feb 22, 2014

  1. timo

    semaphore spec draft

    authored February 22, 2014

Jan 07, 2014

  1. Larry Wall

    change :times to :limit

    authored January 07, 2014

Dec 10, 2013

  1. lizmat

    done/quit are named parameters + eternaleye++ suggestions

    authored December 10, 2013

Dec 08, 2013

  1. lizmat

    Fix copy-n-pasto

    authored December 08, 2013

Nov 22, 2013

  1. Larry Wall

    close a channel with .close

    authored November 22, 2013
  2. Jonathan Worthington

    Channels and Supplies should be top-level sections

    authored November 22, 2013

Nov 21, 2013

  1. Larry Wall

    add vim line

    authored November 21, 2013
  2. Larry Wall

    change fail/catch to quit/quit

    authored November 21, 2013

Nov 20, 2013

  1. lizmat

    Fix TAB pollution

    authored November 20, 2013

Nov 19, 2013

  1. lizmat

    Remove (+=) and friends cas operators

    authored November 19, 2013
  2. Larry Wall

    s/fail/catch/ on receiving end, tap has named args

    authored November 19, 2013
  3. Larry Wall

    winner ~~ s/nobody/wait 0/

    authored November 19, 2013

Nov 18, 2013

  1. lizmat

    Some more simplification: re-introduce winner *

    authored November 19, 2013
  2. lizmat

    Remove direct params from winner ... {}

    That list should be automagically created from whatever was specified with
    the done $foo { } statements
    authored November 18, 2013
  3. Larry Wall

    s/later/nobody/

    authored November 18, 2013
  4. Larry Wall

    remove sig collision with placeholders

    authored November 17, 2013

Nov 17, 2013

  1. lizmat

    Remove Channel.peek, it is too dangerous

    And a remnant from Thread times.
    authored November 18, 2013
  2. lizmat

    Some close/done fiddling, plus the -> a sender

    Which makes we wonder, whether we shouldn't have a "keeper" for channels as
    well.
    authored November 18, 2013
Something went wrong with that request. Please try again.