On Thu, 14 Sep 2017 17:47:59 -0700, alex.jakime...@gmail.com wrote:
> but I guess it is possible to store the index of the current enum value and
> simply increment/decrement it when needed.
That's trading more RAM for performance increase that's likely inconsequential
in nearly all use cases. T
On Thu, 14 Sep 2017 17:47:59 -0700, alex.jakime...@gmail.com wrote:
> but I guess it is possible to store the index of the current enum value and
> simply increment/decrement it when needed.
That's trading more RAM for performance increase that's likely inconsequential
in nearly all use cases. T
I just committed a hotfix so the upcoming release can go through.
Hopefully it can be replaced with a proper implementation of optional
parameters for the nativecall compiler soon.
https://github.com/rakudo/rakudo/commit/1818de980fe39a37b405c0353d088932bd4d034a
I just committed a hotfix so the upcoming release can go through.
Hopefully it can be replaced with a proper implementation of optional
parameters for the nativecall compiler soon.
https://github.com/rakudo/rakudo/commit/1818de980fe39a37b405c0353d088932bd4d034a
On Wed, 01 Feb 2017 13:11:21 -0800, j...@gellyfish.co.uk wrote:
> With 6.d.PREVIEW the simplest code for IO::Socket::Async mis-behaves:
>
> use v6.d.PREVIEW;
>
> react {
> whenever IO::Socket::Async.listen('localhost', ) -> $conn {
> whenever $conn.Supply(:bin) ->
On Wed, 01 Feb 2017 13:11:21 -0800, j...@gellyfish.co.uk wrote:
> With 6.d.PREVIEW the simplest code for IO::Socket::Async mis-behaves:
>
> use v6.d.PREVIEW;
>
> react {
> whenever IO::Socket::Async.listen('localhost', ) -> $conn {
> whenever $conn.Supply(:bin) ->
On Thu, 14 Sep 2017 13:30:46 -0700, timo wrote:
> I'm using two start blocks that return Slips to generate a long list in
> parallel, then i iterate over the result in the Moar Heap Analyzer.
>
> Trying to take advantage of v6.d's nonblocking await gives me a change
> in semantics, though:
>
>
On Thu, 14 Sep 2017 13:30:46 -0700, timo wrote:
> I'm using two start blocks that return Slips to generate a long list in
> parallel, then i iterate over the result in the Moar Heap Analyzer.
>
> Trying to take advantage of v6.d's nonblocking await gives me a change
> in semantics, though:
>
>
On Tue, 08 Dec 2015 05:40:29 -0800, pub.clau...@gmail.com wrote:
> The replacement of the 'whatever' syntax as sugar for consuming Channels
> through 'react' locks very often (5-10% of the time). The thread seems to
> be stuck on 'shift', probably from the Channel). When rewriting the exact
> same
On Tue, 08 Dec 2015 05:40:29 -0800, pub.clau...@gmail.com wrote:
> The replacement of the 'whatever' syntax as sugar for consuming Channels
> through 'react' locks very often (5-10% of the time). The thread seems to
> be stuck on 'shift', probably from the Channel). When rewriting the exact
> same
On Thu, 14 Sep 2017 18:03:16 -0700, alex.jakime...@gmail.com wrote:
> Actually, another direct implication of using .first is this:
>
> Code:
> enum Animal (Cat => 0, Dog => 0, Human => 42);
> say Dog.succ
>
> Result:
> Dog
>
>
> So it's not just the algorithmic complexity, and we need a test f
On Thu, 14 Sep 2017 18:03:16 -0700, alex.jakime...@gmail.com wrote:
> Actually, another direct implication of using .first is this:
>
> Code:
> enum Animal (Cat => 0, Dog => 0, Human => 42);
> say Dog.succ
>
> Result:
> Dog
>
>
> So it's not just the algorithmic complexity, and we need a test f
On Sat, 23 Jul 2016 20:36:59 -0700, c...@zoffix.com wrote:
> Blockless `react` seems to be unsupported and the error message it
> throws is cryptic and unrelated to the actual issue. Best would be if
> it actually worked, but at least the error message should be improved.
>
> $ perl6 -e 'react whe
On Sat, 23 Jul 2016 20:36:59 -0700, c...@zoffix.com wrote:
> Blockless `react` seems to be unsupported and the error message it
> throws is cryptic and unrelated to the actual issue. Best would be if
> it actually worked, but at least the error message should be improved.
>
> $ perl6 -e 'react whe
Well, the title says “Enum.succ and Enum.pred are O(n)” and the issue is still
there, so this ticket is definitely not resolved. If anything, it was rejected.
However, the reasoning for keeping O(n) kinda contradicts itself. If we're
trading RAM for performance, and the amount of elements in enums
Now resolved in
https://github.com/rakudo/rakudo/commit/f925c64826f78803969bb43398877309f6b4a1ac
Closing.
On 2017-09-15 09:01:04, alex.jakime...@gmail.com wrote:
> Well, the title says “Enum.succ and Enum.pred are O(n)” and the issue
> is still
> there, so this ticket is definitely not resolved.
On Tue, 05 Sep 2017 03:19:45 -0700, zef...@fysh.org wrote:
> > (3, Nil)
> (3 Nil)
> > List.new(3, Nil)
> (3 (Any))
>
> It is possible (as it should be) to put Nil into a List, if it's
> constructed using the comma operator. But constructing it via the
> List.new() constructor replaces the Nil wit
On Tue, 05 Sep 2017 03:19:45 -0700, zef...@fysh.org wrote:
> > (3, Nil)
> (3 Nil)
> > List.new(3, Nil)
> (3 (Any))
>
> It is possible (as it should be) to put Nil into a List, if it's
> constructed using the comma operator. But constructing it via the
> List.new() constructor replaces the Nil wit
On Fri, 15 Sep 2017 11:47:10 -0700, c...@zoffix.com wrote:
> On Tue, 05 Sep 2017 03:19:45 -0700, zef...@fysh.org wrote:
> > > (3, Nil)
> > (3 Nil)
> > > List.new(3, Nil)
> > (3 (Any))
> >
> > It is possible (as it should be) to put Nil into a List, if it's
> > constructed using the comma operator.
Well, as long as it benefits the "very fucking close", amirite?
Take care of the conch.
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #132097]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132097 >
Submitting this ticket just to add some context for the upcoming test
On Sun, 16 Apr 2017 12:56:58 -0700, elizabeth wrote:
> Actually reported as a SO question by brian d foy:
>
> http://stackoverflow.com/questions/43437664/how-can-i-get-around-a-
> slurpy-parameter-in-the-perl-6-signature
>
>
> m: my @a = [1,1],[2,2],[3,3]; dd @a; @a.splice: 0, 2,
> $[4,4
On Mon, 02 Jan 2017 16:35:46 -0800, comdog wrote:
> Trying to output a character unrepresentable in the specified
> encoding throws an X::AdHoc error. I think that should be X::IO,
> and maybe there's enough issues here that an X::IO::Exception may
> be interesting enough.
>
> my $file = 'enco
23 matches
Mail list logo
