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

Bool.perl returns object without value #2559

Closed
p6rt opened this issue Nov 23, 2011 · 4 comments
Closed

Bool.perl returns object without value #2559

p6rt opened this issue Nov 23, 2011 · 4 comments

Comments

@p6rt
Copy link

p6rt commented Nov 23, 2011

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

Searchable as RT104430$

@p6rt
Copy link
Author

p6rt commented Nov 23, 2011

From @bbkr

Spec is not very precise about perl() method, but current behavior is for sure
LTA for Bool type​:

$ perl6 -e 'True.perl.say'
Bool.new()

Value is lost because "so Bool.new()" is False.

Another side effect is that one can get unexpected mix of object types and
values like​:

nom​: any(True, 1).say
nom 4a57bd​: OUTPUT«any(Bool.new(), 1)â�¤Â»

[15​:17] <jnthn> bbkr​: Yeah, that stringification is LTA

[15​:24] <lumi_> bbkr​: Also maybe junction needs a .gist method?

@p6rt
Copy link
Author

p6rt commented Nov 26, 2011

From @jnthn

On Wed Nov 23 06​:58​:41 2011, pawel.pabian@​implix.com wrote​:

Spec is not very precise about perl() method, but current behavior is
for sure
LTA for Bool type​:

$ perl6 -e 'True.perl.say'
Bool.new()

Value is lost because "so Bool.new()" is False.

Another side effect is that one can get unexpected mix of object types
and
values like​:

nom​: any(True, 1).say
nom 4a57bd​: OUTPUT«any(Bool.new(), 1)â�¤Â»

[15​:17] <jnthn> bbkr​: Yeah, that stringification is LTA

[15​:24] <lumi_> bbkr​: Also maybe junction needs a .gist method?

This has been patched and tests added in recent days, so resolving it now.

Thanks,

/jnthn

@p6rt
Copy link
Author

p6rt commented Nov 26, 2011

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

@p6rt
Copy link
Author

p6rt commented Nov 26, 2011

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

@p6rt p6rt closed this as completed Nov 26, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant