microsoft / microsoft/TypeScript
Proposal: The internal modifier for classes
Nessuno ha ancora preso questa issue.
- Lingua principale
- Go
- Stelle
- 111k
- Fork
- 14.4k
- Merge medio
- 1g 19h
- PR unite (30g)
- 117
Descrizione
The internal modifier
Often there is a need to share information on types within a program or package that should not be
accessed from outside of the program or package. While the public accessibility modifier allows
types to share information, is insufficient for this case as consumers of the package have access
to the information. While the private accessibility modifier prevents consumers of the package
from accessing information from the type, it is insufficient for this case as types within the
package also cannot access the information. To satisfy this case, we propose the addition of the
internal modifier to class members.
Goals
This proposal aims to describe the static semantics of the internal modifier as it applies to members of a class (methods, accessors, and properties).
Non-goals
This proposal does not cover any other use of the internal modifier on other declarations.
Static Semantics
Visibility
Within a non-declaration file, a class member marked internal is treated as if it had public
visibility for any property access:
source.ts:
class C {
internal x: number;
}
let c = new C();
c.x = 1; // ok
When consuming a class from a declaration file, a class member marked internal is treated as
if it had private visibility for any property access:
declaration.d.ts
class C {
internal x: number;
}
source.ts
/// <reference path="declaration.d.ts" />
let c = new C();
c.x = 1; // error
Assignability
When checking assignability of types within a non-declaration file, a class member marked
internal is treated as if it had public visibility:
source.ts:
class C {
internal x: number;
}
interface X {
x: number;
}
let x: X = new C(); // ok
If one of the types is imported or referenced from a declaration file, but the other is defined
inside of a non-declaration file, a class member marked internal is treated as if it had
private visibility:
declaration.d.ts
class C {
internal x: number;
}
source.ts
/// <reference path="declaration.d.ts" />
interface X {
}
let x: X = new C(); // error
It is important to allow assignability between super- and subclasses from a declaration file
with overridden members marked internal. When both types are imported or referenced from a
declaration file, a class member marked internal is treated as if it had protected visibility:
declaration.d.ts
class C {
internal x(): void;
}
class D extends C {
internal x(): void;
}
source.ts
/// <reference path="declaration.d.ts" />
let c: C = new D(); // ok
However, this does not carry over to subclasses that are defined in a non-declaration file:
declaration.d.ts
class C {
internal x(): void;
}
source.ts
/// <reference path="declaration.d.ts" />
class D extends C {
internal x(): void; // error
}
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Direzione di ricerca
Inizia studiando le sezioni della proposta sulla semantica statica e i relativi esempi per la visibilità e l'assegnabilità dei membri nei file di dichiarazione e nei file non di dichiarazione. Il lavoro è completo quando il internal modifier si comporta in modo coerente con le regole indicate per public, private e protected, inclusi i membri sovrascritti e il caso della sottoclasse in un file non di dichiarazione.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- typescript
- Ambito
- compilers
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 25/100