Enhancement to assigning variables quickly via constructors #11707
Comments
|
Removed Type-Defect label. |
|
Removed this from the Later milestone. |
|
Removed Oldschool-Milestone-Later label. |
|
This comment was originally written by @kaendfinger This would be another nice addition. |
|
This comment was originally written by @seaneagan I don't see how it could be sugar for calling a parent constructor because you wouldn't want changing the name of a positional constructor parameter to break subclasses, and if it assumes calling the same-named constructor of the superclass, then that probably prevents it from being used in many cases. |
DartBot
added
Type-Enhancement
area-language
kevmoo
added
type-enhancement
|
It's not clear to me what this is actually proposing. If it sidesteps the superclass's constructor and assigns its field directly, that's bad. It violates the superclass's own encapsulation. A class should be able to ensure all instantiations go through its own constructors so it can enforce its preconditions and invariants. If it is calling the superclass's constructor, it's not clear how it knows which constructor to call and which arguments to pass for what. I'm going to go ahead and close this because I don't think we intend to take action on it. Though, for what it's worth, I have found myself wishing for something similar on occasion. Once you get used to |
munificent
added
the
closed-not-planned
This issue was originally filed by ayman.ga...@gmail.com
This is an enhancement type, can't find it in templates.
== current way of quick assigning properties via constructor :
class Person {
String name;
Person(this.name);
String greet() => 'Hello, $name';
}
class Employee extends Person {
num salary;
Employee(String name, this.salary) : super(name);
}
== proposed way:
class Person {
String name;
Person(this.name);
String greet() => 'Hello, $name';
}
class Employee extends Person {
num salary;
Employee(super.name, this.salary);
}
The text was updated successfully, but these errors were encountered: