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

NativeCall doesn't error about unusable types until runtime #4444

Closed
p6rt opened this issue Jul 28, 2015 · 5 comments
Closed

NativeCall doesn't error about unusable types until runtime #4444

p6rt opened this issue Jul 28, 2015 · 5 comments

Comments

@p6rt
Copy link

p6rt commented Jul 28, 2015

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

Searchable as RT125706$

@p6rt
Copy link
Author

p6rt commented Jul 28, 2015

From @hoelzro

For example, if you use Bool with a native sub, you don't get an error until you actually try to run that function. It would be Awesome if NativeCall could tell you about invalid signatures at compile time.

@p6rt
Copy link
Author

p6rt commented Jul 28, 2015

From @FROGGS

Aye, we only check the arity until now​: https://github.com/rakudo/rakudo/blob/nom/lib/NativeCall.pm#L240

And even that is not compile time...
I have no idea though how to implement compile time checking for signatures there. Mind that rakudo's optimizer does that for non-NativeCall subs.

@p6rt
Copy link
Author

p6rt commented Jul 28, 2015

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

@p6rt
Copy link
Author

p6rt commented Jan 1, 2016

From @timo

Skarsnik implemented a sanity checking routine as well as tests in rakudo commit 532c11abbcc8409a03d4a585296149f94c219e08

@p6rt
Copy link
Author

p6rt commented Jan 1, 2016

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

@p6rt p6rt closed this as completed Jan 1, 2016
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