“? doesn't imply truth it implies a question”
This is an interesting point actually. pmurias++ expressed the same idea.
I find it hard to understand this fully, but I guess I'll have to accept that
there are different ways to think about it :)
For example:
“The ? prefix asks an expression
For those reading this on RT, here's the previous comment in a readable way:
I wouldn't be so eager to judge the proposal based on the original post.
Sometimes I submit tickets fast, and sometimes ideas are not conveyed as
clearly as I assumed.
“How are those things related?”
These were the
I wouldn't be so eager to judge the proposal based on the original post.
Sometimes I submit tickets fast, and sometimes ideas are not conveyed as
clearly as I assumed.
“How are those things related?”
These were the examples of the pair syntax (what works and what doesn't). Now,
?↔! pattern is
The OP said :?foo should work because :foo and :!foo work. I don't follow
the logic. How are those things related? Why should :foo and :!foo imply
:?foo? (In my head it makes as much sense as ":foo and :!foo implies
:*foo", which is to say, none.)
I don't see any benefit to adding a :?foo
2¢:
? doesn't imply truth it implies a question. The ? prefix asks an
expression whether it's True or False. When used as a sigil like $?FILE
it's asking the compiler about something.
‘:foo’ sets foo to True. ‘:!foo’ sets it to False. ‘:?foo’ looks like it's
trying to ask something a question,
2¢:
? doesn't imply truth it implies a question. The ? prefix asks an
expression whether it's True or False. When used as a sigil like $?FILE
it's asking the compiler about something.
‘:foo’ sets foo to True. ‘:!foo’ sets it to False. ‘:?foo’ looks like it's
trying to ask something a question,
Yes, I should have been more clear.
Basically, it should work like (:foo) does, which is construct foo => True
pair.
On 2017-07-22 19:25:19, lloyd.fo...@gmail.com wrote:
> Sorry for being think but what is
> say (:?foo);
> meant to do? The OP just says it should "work".
>
> On Sun, Jul 23, 2017
Sorry for being think but what is
say (:?foo);
meant to do? The OP just says it should "work".
On Sun, Jul 23, 2017 at 6:05 AM Aleks-Daniel Jakimenko-Aleksejev via RT <
perl6-bugs-follo...@perl.org> wrote:
> sub foo($bar!) { say $bar }; foo(42)
>
> On 2017-07-22 11:19:41,
Sorry for being think but what is
say (:?foo);
meant to do? The OP just says it should "work".
On Sun, Jul 23, 2017 at 6:05 AM Aleks-Daniel Jakimenko-Aleksejev via RT <
perl6-bugs-follo...@perl.org> wrote:
> sub foo($bar!) { say $bar }; foo(42)
>
> On 2017-07-22 11:19:41,
Perhaps also worth noting that this applies to other holes as well, e.g. those
created by extending an array:
my @a = 42; @a[5] = 49; say |@a # 42(Mu)(Mu)(Mu)(Mu)49
In fact, this the actual problem the user had.
On 2017-07-22 18:52:03, c...@zoffix.com wrote:
> On Sat, 22 Jul 2017 18:48:38
On Sat, 22 Jul 2017 18:48:38 -0700, c...@zoffix.com wrote:
> The current behaviour kinda makes sense when you squint at it, but
> today we had a user[^1]who was surprised by it, so I'm filing it as a
> ticket, if maybe there's some Better Way this can be done with.
>
> When you :delete an element
On Sat, 22 Jul 2017 18:48:38 -0700, c...@zoffix.com wrote:
> The current behaviour kinda makes sense when you squint at it, but
> today we had a user[^1]who was surprised by it, so I'm filing it as a
> ticket, if maybe there's some Better Way this can be done with.
>
> When you :delete an element
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131783]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131783 >
The current behaviour kinda makes sense when you squint at it, but today we had
a
I bisected it to
https://github.com/rakudo/rakudo/commit/40a953f5d9f5c661d8cf9b043643002d348a2000
On earlier rakudo versions it seems to be working fine. I haven't seen it crash
once on anything earlier, but it is *very* slow on rakudos that old, so it's
hard to tell.
nqp changes:
I'm not sure if this is closable. The regression is no longer there, so I'll
remove the tag, but here's a problem:
Code:
say (4,5,6).tail(-2**63+4)
Result:
()
Code:
say (4,5,6,7).tail(-2**63+4)
Result:
Cannot unbox 64 bit wide bigint into native integer
in block at -e line 1
It feels like
sub foo($bar!) { say $bar }; foo(42)
On 2017-07-22 11:19:41, alex.jakime...@gmail.com wrote:
> Eh. The effort required to implement the feature is much less than
> having
> discussions *like this*. I'll try to be quick.
>
> “there's large possibility of introducing some unwanted ambiguity
>
I’m inclined to WONTFIX, as other, much more common, indexing operation suffer
from the same issue:
$ 6 'my @a; say @a[999]'
Cannot unbox 64 bit wide bigint into native integer
$ 6 'my @a[999]'
Illegal dimension in shape: 999. All dimensions must
I’m inclined to WONTFIX, as other, much more common, indexing operation suffer
from the same issue:
$ 6 'my @a; say @a[999]'
Cannot unbox 64 bit wide bigint into native integer
$ 6 'my @a[999]'
Illegal dimension in shape: 999. All dimensions must
Eh. The effort required to implement the feature is much less than having
discussions *like this*. I'll try to be quick.
“there's large possibility of introducing some unwanted ambiguity somewhere”
A good thing to keep in mind indeed.
I don't really like these discussions before actual PRs, but
On Sat, 22 Jul 2017 07:53:26 -0700, alex.jakime...@gmail.com wrote:
> This should work:
>
> Code:
> say (:?foo);
>
> Result:
> ===SORRY!=== Error while compiling -e
> Bogus statement
> at -e:1
> --> say (:⏏?foo);
> expecting any of:
> colon pair
>
>
> Because these work:
>
>
On Sat, 22 Jul 2017 07:53:26 -0700, alex.jakime...@gmail.com wrote:
> This should work:
>
> Code:
> say (:?foo);
>
> Result:
> ===SORRY!=== Error while compiling -e
> Bogus statement
> at -e:1
> --> say (:⏏?foo);
> expecting any of:
> colon pair
>
>
> Because these work:
>
>
On Fri, 07 Apr 2017 19:16:17 -0700, alex.jakime...@gmail.com wrote:
> This no longer prints 256.
>
> Bisectable points to
> https://github.com/rakudo/rakudo/commit/5401a1aa8f12c360ccd3e4000dcdc65ad98c746a
>
> Is it actually resolved or not?
>
> I will mark it testneeded for now (if it's not
Hi all!
Some time ago I solved this problem - https://projecteuler.net/problem=343 -
using a relatively slow pypy3 program (see
https://github.com/shlomif/project-euler/blob/master/project-euler/343/euler_343_v1.py
). After gaining access to the problem's forum, I found a faster way to solve
it
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #131781]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131781 >
This should work:
Code:
say (:?foo);
Result:
===SORRY!=== Error
A test was added in
https://github.com/perl6/roast/commit/84e5309567a5f3ee0d1d7450e08225119b08f3af
dogbert17++
On 2017-07-21 12:46:12, jan-olof.hen...@bredband.net wrote:
> On Sat, 14 Nov 2015 14:06:52 -0800, grond...@yahoo.fr wrote:
> > $ perl6 --version
> > This is perl6 version
On 07/22/2017 12:03 PM, Aleks-Daniel Jakimenko-Aleksejev via RT wrote:
> Is there any code snippet to reproduce it?
>
> The backtrace mentions mongo-perl6-driver…
True, its in the mongodb driver project. The test is in the attachment
and it crashed around line
98 or 99. Just finished the 'Find
On 07/22/2017 12:03 PM, Aleks-Daniel Jakimenko-Aleksejev via RT wrote:
Is there any code snippet to reproduce it?
The backtrace mentions mongo-perl6-driver…
True, its in the mongodb driver project. The test is in the attachment
and it crashed around line
98 or 99. Just finished the 'Find
Is there any code snippet to reproduce it?
The backtrace mentions mongo-perl6-driver…
On 2017-07-22 02:38:03, mt1...@gmail.com wrote:
> Test code erred in perl6 version 2017.07-31-g895bdc8 built on MoarVM
> version 2017.07.
>
> Regards,
> Marcel
>
>
> The crash dump;
>
>
> *** Error in
# New Ticket Created by mt1957
# Please include the string: [perl #131780]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131780 >
Test code erred in perl6 version 2017.07-31-g895bdc8 built on MoarVM
version 2017.07.
29 matches
Mail list logo
