Perl6 RFC Librarian wrote: >> =head1 DESCRIPTION > > What is currently an optimization for pseudo-hashes: > > my Dog $spot = Dog->new(); > > should be replaced with: > > my Dog $spot; > > which calls an implicit constructor (discussed further in the IMPLEMENTATION > section). The optimization behaviour can be retained in some form (see the > MIGRATION section). My previous concerns have not been adressed: - There may not be a default constructor - This makes creations of Singleton classes impossible - There is a good reason to created typed, but undef, references and fill them in later. > For example, the syntax: > > my Dog $spot = "Spot"; > > would be transformed to, or be the equivalent of: > > $spot = Dog->$METHOD("Spot"); Based on my C++ experience, this should only be allowed if the constructor has been marked as 'implicit construction safe'. Hildo
- RFC 171 (v2) my Dog $spot should call a constructor im... Perl6 RFC Librarian
- Re: RFC 171 (v2) my Dog $spot should call a const... Michael Fowler
- Re: RFC 171 (v2) my Dog $spot should call a const... Nathan Wiger
- Re: RFC 171 (v2) my Dog $spot should call a c... Michael Fowler
- Re: RFC 171 (v2) my Dog $spot should call... Nathan Wiger
- Re: RFC 171 (v2) my Dog $spot should ... Tom Christiansen
- Re: RFC 171 (v2) my Dog $spot sh... Michael Fowler
- Re: RFC 171 (v2) my Dog $spot should ... Michael Fowler
- Re: RFC 171 (v2) my Dog $spot should call a const... Hildo Biersma
- Re: RFC 171 (v2) my Dog $spot should call a c... Michael Fowler
- Re: RFC 171 (v2) my Dog $spot should call... Hildo Biersma
- Re: RFC 171 (v2) my Dog $spot should ... Michael Fowler
- Re: RFC 171 (v2) my Dog $spot sh... Michael Fowler
- Re: RFC 171 (v2) my Dog $spot should call a c... Piers Cawley
- Re: RFC 171 (v2) my Dog $spot should call... Bart Lateur
- Re: RFC 171 (v2) my Dog $spot should ... Hildo Biersma
- Re: RFC 171 (v2) my Dog $spot should ... Michael Fowler
- Re: RFC 171 (v2) my Dog $spot should ... Damian Conway
- Re: RFC 171 (v2) my Dog $spot sh... Nick Ing-Simmons