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
Multiple dispatch doesn't treat 'rw' parameters as narrower than readonly parameters in Rakudo #1695
Comments
From @masak<masak> rakudo: multi foo(Int $x is rw) { say "writable" }; multi |
From @cokeOn Fri Apr 16 01:31:22 2010, masak wrote:
Behavior is mostly unchanged since 2010 - error message has better signature reporting, but still reported as ambiguous. 20:36 <[Coke]> m: multi foo(Int $x is rw) { say "writable" }; multi foo(Int $x) |
The RT System itself - Status changed from 'new' to 'open' |
From @peschwaOn Sat Feb 22 17:37:47 2014, coke wrote:
With Rakudo commits 8cba8863 and ed10656c this now behaves as follow: 15:52 < psch> m: multi foo(Int $x is rw) { say "writable" }; multi foo(Int $x) { "readonly" }; say foo(42); foo my $ = 42; I've also added S06-multi/by-trait.t to spectest.data which tests this. |
From @jnthnOn Tue Nov 10 07:55:06 2015, peschwa@gmail.com wrote:
psch++ also updated most of the multi-dispatch caching logic to get things performing well again. Today I updated the dynamic optimizer in Moar to understand the new multi-dispatch flag, so we don't go mis-inlining. And fixed a further static optimizer issue where it wasn't aware of `is rw` and so could mis-dispatch. Both covered by more tests in S06-multi/by-trait.t. So, we can consider this done. /jnthn |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#74414 (status was 'resolved')
Searchable as RT74414$
The text was updated successfully, but these errors were encountered: