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

Self-Referential Junctions Need .gistseen #4890

Open
p6rt opened this issue Dec 18, 2015 · 4 comments
Open

Self-Referential Junctions Need .gistseen #4890

p6rt opened this issue Dec 18, 2015 · 4 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Dec 18, 2015

Migrated from rt.perl.org#126961 (status was 'open')

Searchable as RT126961$

@p6rt
Copy link
Author

p6rt commented Dec 18, 2015

From @MadcapJake

perl6 -e 'my $a = 10; $a ^= 2; say $a' hangs indefinitely.

On irc, camelia outputs​:
rakudo-moar 71dadb​: OUTPUT«Memory allocation failed; could not
allocate 2210832 bytes␤»

And my version​:
$ perl6 -v
This is rakudo version 2015.11-419-gb7f0bcc built on MoarVM version
2015.11-34-gc3eea17 implementing Perl v6.b.

@p6rt
Copy link
Author

p6rt commented Apr 26, 2017

From @zoffixznet

On Fri, 18 Dec 2015 11​:06​:44 -0800, madcap.russo@​gmail.com wrote​:

perl6 -e 'my $a = 10; $a ^= 2; say $a' hangs indefinitely.

On irc, camelia outputs​:
rakudo-moar 71dadb​: OUTPUT«Memory allocation failed; could not
allocate 2210832 bytes␤»

And my version​:
$ perl6 -v
This is rakudo version 2015.11-419-gb7f0bcc built on MoarVM version
2015.11-34-gc3eea17 implementing Perl v6.b.

The hang is due to trying to output self-referential Junctions. Seems it needs the same `.gistseen` fix, like we have for Lists and Maps.

$ perl6 -e 'my $a = 10; $a = one($a, 2); ' # doesn't hang
$ perl6 -e 'my $a = 10; $a = one($a, 2); $a.perl' # hangs
$ perl6 -e 'my $a = 10; $a = all($a, 2); $a.perl' # hangs

@p6rt
Copy link
Author

p6rt commented Apr 26, 2017

The RT System itself - Status changed from 'new' to 'open'

@p6rt p6rt added the Bug label Jan 5, 2020
@raiph
Copy link

raiph commented Mar 20, 2021

The fix has presumably been applied. Wfm on 2020.12.

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

2 participants