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
Comments
From @hoelzroFor 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. |
From @FROGGSAye, 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... |
The RT System itself - Status changed from 'new' to 'open' |
From @timoSkarsnik implemented a sanity checking routine as well as tests in rakudo commit 532c11abbcc8409a03d4a585296149f94c219e08 |
@timo - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125706 (status was 'resolved')
Searchable as RT125706$
The text was updated successfully, but these errors were encountered: