Add access modifiers to MuranoPL methods and properties
Registered by
Stan Lagun
Currently all MuranoPL properties and methods are considered to be public (as in Python). The problem with such approach is that there is no clear way to distinguish between class public contracts and implementation details. Because there is no way to restrict access to class methods class author cannot modify any implementation methods without having a risk to break some class user. If we have ability to mark properties and methods as public, private, protected and internal (package-level access) it would become possible to restrict access and to properties and methods and thus simplify class maintenance and versionning
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Stan Lagun
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)