Repository navigation
Destructured parameter properties do not introduce properties into their respective class #1541
Description
class C {
constructor(public [x, y, z]: string[]) {
}
}
var c = new C([]);
c.x === c.y;which gives us
error TS2339: Property 'x' does not exist on type 'C'
error TS2339: Property 'y' does not exist on type 'C'
The question is should we be adding properties when destructuring in the face of a visibility modifier?
Activity
DanielRosenwasser commentedon Jan 13, 2015
jonathandturner and I spoke offline and decided that the binding parameters should introduce properties of the appropriate visibility.
DanielRosenwasser commentedon Jan 14, 2015
Anders Hejlsberg (@ahejlsberg) and I spoke offline and decided that binding parameters should not introduce properties of the appropriate visibility.
mhegazy commentedon Jan 15, 2015
Reopening to update the spec.
DanielRosenwasser commentedon Jan 15, 2015
This is Fixed as far as the work goes; the spec work needs to be done.
danquirk commentedon Jan 15, 2015
Let's create new bugs for spec work, that way you can close this with the fixed label. Otherwise we should remove the fixed label from this one, which then makes confusing the fact that it does represent dev work that fixed an issue.
DanielRosenwasser commentedon Jan 16, 2015
Agreed; I've opened up #1691 instead.