Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't parse 'state $i++' in Rakudo (but parses in STD) #2964

Closed
p6rt opened this issue Nov 5, 2012 · 5 comments
Closed

Can't parse 'state $i++' in Rakudo (but parses in STD) #2964

p6rt opened this issue Nov 5, 2012 · 5 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Nov 5, 2012

Migrated from rt.perl.org#115614 (status was 'resolved')

Searchable as RT115614$

@p6rt
Copy link
Author

p6rt commented Nov 5, 2012

From @masak

<TimToady> nr​: constant @​c = 1, { state $i++; 2 * (2 * $i - 1) / ($i +
1) * $_ } ... *; say @​c[$_] for 0..5
<p6eval> niecza v22-16-g4c016f5​: OUTPUT«1␤1␤2␤5␤14␤42␤»
<p6eval> ..rakudo 64208d​: OUTPUT«===SORRY!===␤Preceding context
expects a term, but found infix + instead [...]
<masak> std​: state $i++
<p6eval> std 04216b1​: OUTPUT«ok 00​:00 42m␤»
<masak> TimToady​: nieczabug that 'state $i++' doesn't parse?
<TimToady> rakudobug
<masak> oh!
<masak> yes.
* masak submits rakudobug
<masak> r​: state $i++
<p6eval> rakudo 64208d​: OUTPUT«===SORRY!===␤Confused [...]

@p6rt
Copy link
Author

p6rt commented Oct 27, 2014

From @usev6

Behaviour is the same as two years ago.

I added a test (fudged 'skip') to S04-declarations/state.t with commit​: Raku/roast@ff58ad1b74

@p6rt
Copy link
Author

p6rt commented Oct 27, 2014

@usev6 - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

p6rt commented Mar 28, 2015

From @jnthn

On Mon Oct 27 14​:41​:08 2014, bartolin@​gmx.de wrote​:

Behaviour is the same as two years ago.

I added a test (fudged 'skip') to S04-declarations/state.t with
commit​: Raku/roast@ff58ad1b74

The issue was fixed, and these tests pass now. Unfudged them; resolving ticket.

/jnthn

@p6rt
Copy link
Author

p6rt commented Mar 28, 2015

@jnthn - Status changed from 'open' to 'resolved'

@p6rt p6rt closed this as completed Mar 28, 2015
@p6rt p6rt added the Bug label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant