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
trait 'is default' on attributes has no effect #4640
Comments
From @FROGGSsay class { has Int $.foo is default(0) }.new.foo class Foo { has Int $.foo is default(0) }; say Foo.new.foo I would expect that foo is zero in both cases. |
From @TimToadyOn Sat Oct 10 08:33:13 2015, FROGGS.de wrote:
Even less sensical, it violates its own :D here:
|
1 similar comment
From @TimToadyOn Sat Oct 10 08:33:13 2015, FROGGS.de wrote:
Even less sensical, it violates its own :D here:
|
From @skidsOn Fri, 16 Oct 2015 00:54:21 -0700, larry wrote:
The first case was resolved with RT#131387 The second case seems fixed. Tests specifically for the second case still needed. So maybe combine this with the latter and make a ruling on |
The RT System itself - Status changed from 'new' to 'open' |
From @skidsOn Wed, 13 Sep 2017 19:15:36 -0700, bri@abrij.org wrote:
Ignore that last sentence, I was going to suggest RT#126296 but... |
From @dogbert17On Wed, 13 Sep 2017 19:17:16 -0700, bri@abrij.org wrote:
Second case fixed with commit rakudo/rakudo@148ba7f |
From @AlexDanielTests in Closing. On 2018-03-12 06:59:31, jan-olof.hendig@bredband.net wrote:
|
@AlexDaniel - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#126318 (status was 'resolved')
Searchable as RT126318$
The text was updated successfully, but these errors were encountered: