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

undef cannot be assigned to typed variables in Rakudo #371

Closed
p6rt opened this issue Oct 26, 2008 · 5 comments
Closed

undef cannot be assigned to typed variables in Rakudo #371

p6rt opened this issue Oct 26, 2008 · 5 comments

Comments

@p6rt
Copy link

p6rt commented Oct 26, 2008

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

Searchable as RT60144$

@p6rt
Copy link
Author

p6rt commented Oct 26, 2008

From @masak

Rakudo r32141 fails to accept undef as a value to typed variables.

$ ./perl6 -e 'my Int $a = undef'
Type check failed
[...]

Should work according to S02.

@p6rt
Copy link
Author

p6rt commented Oct 27, 2008

From @pmichaud

On Sun, Oct 26, 2008 at 12​:33​:21PM -0700, Carl Mäsak wrote​:

Rakudo r32141 fails to accept undef as a value to typed variables.

$ ./perl6 -e 'my Int $a = undef'
Type check failed
[...]

Should work according to S02.

Yes, this is a bug in Rakudo. We're likely to be revising all of
assignment and container semantics soon, so this should be done as
part of that.

In general, any container can contain an undefined type (S02), and
per a conversation on #perl6 assigning a Failure object causes
its associated exception to be marked as unhandled [1]. In fact,
I suspect this is true for any cloning of a Failure object.

1. http://irclog.perlgeek.de/perl6/2008-10-27#i_650223

Thanks,

Pm

@p6rt
Copy link
Author

p6rt commented Oct 27, 2008

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

@p6rt
Copy link
Author

p6rt commented Nov 9, 2008

From @moritz

This has been fixed in the mean time, as of r32473 your test case works
for me. Resolving...

@p6rt
Copy link
Author

p6rt commented Nov 9, 2008

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

@p6rt p6rt closed this as completed Nov 9, 2008
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