Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: nom
Commits on May 26, 2015
  1. @timo

    promote last, next and redo to full multi subs

    timo authored
    at some point it had to be changed into this, but
    it seems like it's safe to have it like this now.
    
    the no-arguments version of those will now not only not
    allocate a BOOTArray and a Parcel, but also get jitted
    properly due to not using param_sp (slurpy positional)
    op codes.
  2. @lizmat

    Fix MMD named parameter snafu again

    lizmat authored
    When will I learn that named parameters only serve as tie breakers,
    and that therefore the order of the candidates is important!
  3. @lizmat

    Fix IO::Path(:basename<foo>), spotted by cygx++

    lizmat authored
    Which I broke with e60f85c and which did not
    cause any spectest breakage :-(
  4. @lizmat
  5. @lizmat
  6. @lizmat

    Introduce :&as parameter to .categorize as well

    lizmat authored
    Plus some other associated cleanup with .classify
  7. @FROGGS

    dont create dirs when instanciating CUR

    FROGGS authored
    But also do not skip non-existing locations, because we might be
    creating them when installing into.
  8. @lizmat

    Lose the <unit-outer> in backtraces

    lizmat authored
    The lazification of backtraces accidentally included the <unit-outer> scope,
    where it didn't before.
Commits on May 25, 2015
  1. @lizmat

    Cleanup on Range.pick/roll

    lizmat authored
    Specifically, (^10e6).pick/roll should be much faster now, as it will not
    build the entire list before pick/rolling (it did before).  So in that case,
    it's several orders of magnitude faster.  This is at the expense of a small
    slowdown for the (^10000000).pick/roll case.
  2. @lizmat

    Fix various issues with typed hashes

    lizmat authored
    This is *really* a bandaid to prevent the actual error from occurring.  This
    is *not* to be considered a solution to a potentially deeper problem.  Since
    this will probably change during the course of the GLR, I thought bandaiding
    this would be a good temporary solution.
  3. @lizmat
  4. @lizmat

    Don't allow empty path specification, raydiak++

    lizmat authored
    It functioned as 'current directory' so far, but that can have dangerous
    implications, especially when trying to do an rm-rf on a directory, and you
    lost the directory name somewhere along the way.
  5. @lizmat

    Revert "List|Parcel.eager should only work on instances"

    lizmat authored
    It breaks the JVM badly.
  6. @Mouq

    Enable typing via "has Type method …" (RT #115868)

    Mouq authored
    Copied verbatim from &def_routine.
Commits on May 24, 2015
  1. @lizmat

    Make @a eqv @b 10% faster if not equal

    lizmat authored
    By not enforcing an explicit return in that case
  2. @lizmat
  3. @lizmat
  4. @lizmat
  5. @lizmat
  6. @lizmat
  7. @lizmat
  8. @lizmat

    Introduce :as parameter to classify

    lizmat authored
    Use case:
    my %h = (a => 1, a => 2, b=> 3).classify(*.key, :what(*.value)); say %h.perl
    {:a([1, 2]), :b([3])}<>
    
    Inspired by smls++'s comments at:
      http://irclog.perlgeek.de/perl6/2015-05-24#i_10648933
Commits on May 23, 2015
  1. @moritz
  2. @lizmat
  3. @moritz
  4. @lizmat

    Mention 'use trace'

    lizmat authored
  5. @lizmat
  6. @jnthn

    Lazily construct a DateTime in Compiler.

    jnthn authored
    This takes its BUILD from taking 6% of setting loading down to 2%.
  7. @lizmat
  8. @lizmat
  9. @lizmat

    Revive Devel::Trace as "trace"

    lizmat authored
    While cleaning up, I found some leftover Devel::Trace functionality that
    seemed useful to reinstate now that we have lexical pragma's.
Commits on May 22, 2015
  1. @lizmat
  2. @lizmat

    Privatize Date/DateTime attributes

    lizmat authored
    They were already a mixed bunch, probably because in the past, classes could
    not see private attributes defined in roles.  Should make date / time handling
    quite a bit faster.
  3. @lizmat
  4. @lizmat
Something went wrong with that request. Please try again.