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
inconsistent whether type constraint violation is compile error #4919
Comments
From zefram@fysh.orgIs it legal to compile code that, if executed, would always produce
Both of these contain an assignment expression that would produce an
However, the following two very similar cases don't permit the code to
Note that, like the first pair of cases, I'm not attempting to Making code like this error at compile time impedes the use of the -zefram |
From @skids
This probably bears hashing out on IRC or ML rather than RT (then linking I suspect the eventual answer will be "maybe we should have a flag |
The RT System itself - Status changed from 'new' to 'open' |
From @geekosaurOn Wed, Dec 23, 2015 at 9:40 PM, Zefram <perl6-bugs-followup@perl.org>
Pretty sure better compile time checking is a known issue and was not -- |
Migrated from rt.perl.org#127014 (status was 'open')
Searchable as RT127014$
The text was updated successfully, but these errors were encountered: