This project is read-only.

Please support protected access for class members !!!

Topics: General, Language Specification
Jan 26, 2013 at 1:43 PM

How to develop good class hierarchies without this?

It should be only compiler checked, as private.

It's ugly:

(<any>this).XXXX = v;


Support also private members with same names in the class hierarchy!!!

Or at least let the compiler give a warning



Jan 28, 2013 at 4:19 PM

There is a feature request for 'protected' in the issue tracker:  Please, feel free to up-vote it if it's important to your project.

Jun 28, 2013 at 7:22 PM
As a basic OO tenet, support for protected access is extremely important. I noticed this is currently the 2nd highest voted feature request, and trivial compared to the #1 request (async await keyword). Any chance we can get this before a 1.0 release, please?