# New Ticket Created by Zoffix Znet
# Please include the string: [perl #132258]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132258 >
On Windows, cmd.exe has different quoting for arguments than CreateProcess()
and accordin
Worse still; there doesn't seem to be a way to make `run` work with `cmd.exe`
commands at all. Even if you escape the args yourself properly, they seem to
get butchered by libuv's quoting. There's a
UV_PROCESS_WINDOWS_VERBATIM_ARGUMENTS that'd avoid quoting, though currently we
have it off (so
Worse still; there doesn't seem to be a way to make `run` work with `cmd.exe`
commands at all. Even if you escape the args yourself properly, they seem to
get butchered by libuv's quoting. There's a
UV_PROCESS_WINDOWS_VERBATIM_ARGUMENTS that'd avoid quoting, though currently we
have it off (so
On Wed, 04 Oct 2017 17:34:37 -0700, alex.jakime...@gmail.com wrote:
> See upstream ticket: https://github.com/MoarVM/MoarVM/issues/718
>
> This ticket is needed so that we can have a rakudo release blocker.
Fixed now.
Built HEAD this morning.
On Wed, 04 Oct 2017 17:34:37 -0700, alex.jakime...@gmail.com wrote:
> See upstream ticket: https://github.com/MoarVM/MoarVM/issues/718
>
> This ticket is needed so that we can have a rakudo release blocker.
Fixed now.
Built HEAD this morning.
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #132261]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132261 >
If you convert an Array with holes into a List, it makes sense for holes to be
turned in
On Mon, 24 Jul 2017 01:54:53 -0700, elizabeth wrote:
>
> > On 23 Jul 2017, at 22:27, Sam S. via RT > follo...@perl.org> wrote:
> >
> >> Which then goes back to: what is the use case of Slipping an Array?
> >
> > Same as slipping any other type of Iterable: Fine-grained, elegant
> > flattening and
On Mon, 24 Jul 2017 01:54:53 -0700, elizabeth wrote:
>
> > On 23 Jul 2017, at 22:27, Sam S. via RT > follo...@perl.org> wrote:
> >
> >> Which then goes back to: what is the use case of Slipping an Array?
> >
> > Same as slipping any other type of Iterable: Fine-grained, elegant
> > flattening and
On Wed, 13 Sep 2017 18:27:37 -0700, b...@abrij.org wrote:
>
> "is default(Mu)" works fine on a variable, but runs into syntax issues
> on attributes...
> weirdly... only for Mu.
>
> $ perl6 -e 'my $a is default(Mu);'
> $ perl6 -e 'class A { has $.a is default(Mu); }'
> ===SORRY!=== Error while co
On Wed, 13 Sep 2017 18:27:37 -0700, b...@abrij.org wrote:
>
> "is default(Mu)" works fine on a variable, but runs into syntax issues
> on attributes...
> weirdly... only for Mu.
>
> $ perl6 -e 'my $a is default(Mu);'
> $ perl6 -e 'class A { has $.a is default(Mu); }'
> ===SORRY!=== Error while co
On Tue, 10 Oct 2017 05:56:34 -0700, c...@zoffix.com wrote:
> If you convert an Array with holes into a List, it makes sense for
> holes to be turned in Nils,
> and if you individually AT-POS them, Nil is indeed what you get.
> However, if you .perl or .gist that List,
> or assign it to another Arra
On Tue, 10 Oct 2017 05:56:34 -0700, c...@zoffix.com wrote:
> If you convert an Array with holes into a List, it makes sense for
> holes to be turned in Nils,
> and if you individually AT-POS them, Nil is indeed what you get.
> However, if you .perl or .gist that List,
> or assign it to another Arra
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #132262]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=132262 >
If you enter the Quote braid, then define a new op, and then try to use it in a
block wit
Fixed with dd943eded83edb3753 , tests needed.
> On 7 Oct 2017, at 15:52, (via RT) wrote:
>
> # New Ticket Created by
> # Please include the string: [perl #132236]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132236 >
>
Fixed with dd943eded83edb3753 , tests needed.
> On 7 Oct 2017, at 15:52, (via RT) wrote:
>
> # New Ticket Created by
> # Please include the string: [perl #132236]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=132236 >
>
FWIW it always did that, not a regression.
On 2017-10-05 21:10:39, j.david.l...@gmail.com wrote:
> This short program crashes reliably (with a segmentation fault) on my
> system:
>
> ```
> #!/usr/bin/env perl6
>
> use v6.c;
>
> my $lock = Lock.new;
> my $set = SetHash.new;
> await (^12).map: {
> s
FWIW if anybody is wondering, not a regression. This exact behavior appeared in
2015.12, see
https://gist.github.com/Whateverable/60a3fc6444bd8ccefc88ce982fa00e8f
On 2017-10-05 21:38:49, j.david.l...@gmail.com wrote:
> This program dies after a short but inconsistent run:
>
> ```
> #!/usr/bin/env
I'll close this in favor of the doc issue mentioned above.
I'm pretty sure this needs a corresponding [DETRAP] ticket, but that tag is not
a thing *yet*. For now we only document these things. Eventually I'll get to
it, but this a long-term thingie (like v6.d or v6.e or whatever).
On 2017-10-09 0
FWIW it went from 4.1724 to 3.3393 (2015.12→HEAD(a72214c)) for 5k of says.
On 2016-01-24 06:28:38, n...@detonation.org wrote:
> I don't think it's related to subs. It's compilation in general that's
> rather slow, most of all parsing.
>
> nine@sphinx:~> for x in {1..1}; do echo 'say ‘a’;' >> pr
Well, the crash is no longer there, but it shouldn't be a VMNull.
This problem was observed again today in this discussion:
http://colabti.org/irclogger/irclogger_log/perl6?date=2017-10-11#l104
On 2016-05-11 05:05:20, sml...@gmail.com wrote:
> Similarly to ticket #127254, this does not segfault
I don't know if this should be implemented. But at the same time, isn't it just
a matter of using an arg alias?
On 2016-01-05 05:29:15, elizabeth wrote:
> > On 05 Jan 2016, at 02:49, Alex Jakimenko (via RT) > follo...@perl.org> wrote:
> >
> > # New Ticket Created by Alex Jakimenko
> > # Please in
I'm fairly sure that the ship for this has sailed, we've had this “issue” for a
year now.
I guess during that year everyone has adapted their code to the new behavior.
So if you're reading this comment and you think that the ticket should be
closed, please just mark it as ｢testneeded｣ so that we
This runs reliably when you let the lock-protected block return
something unrelated to the hash:
#!/usr/bin/env perl6
use v6.c;
my $lock = Lock.new;
my $set = SetHash.new;
await (^12).map: {
start {
for (^1000) {
$lock.protect: { $set<1> = True }
$lock.protect
This runs reliably when you let the lock-protected block return
something unrelated to the hash:
#!/usr/bin/env perl6
use v6.c;
my $lock = Lock.new;
my $set = SetHash.new;
await (^12).map: {
start {
for (^1000) {
$lock.protect: { $set<1> = True }
$lock.protect
It's a bit tricky to get a proper backtrace dump out of gdb for this,
but what I'm seeing is this:
this source file calls sink on a value from outside the protected lock,
which runs the FETCH of the SetHash, which calls nqp::existskey on the
internal elems hash.
That part is explosive, presumably
It's a bit tricky to get a proper backtrace dump out of gdb for this,
but what I'm seeing is this:
this source file calls sink on a value from outside the protected lock,
which runs the FETCH of the SetHash, which calls nqp::existskey on the
internal elems hash.
That part is explosive, presumably
26 matches
Mail list logo
