Skip to content

Code visibility and scoping #59984

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
lafrank opened this issue Jan 26, 2025 · 3 comments
Closed

Code visibility and scoping #59984

lafrank opened this issue Jan 26, 2025 · 3 comments
Labels
area-language Dart language related items (some items might be better tracked at github.com/dart-lang/language). closed-duplicate Closed in favor of an existing report triage-automation See https://github.com/dart-lang/ecosystem/tree/main/pkgs/sdk_triage_bot. type-question A question about expected behavior or functionality

Comments

@lafrank
Copy link

lafrank commented Jan 26, 2025

I understnd this not going to be a well-formatted issue since it is rather a language design question.

Based on issue #33383 which is 5 years old now I am wondering if any plans to finally add public, private and protected visibility modifiers to the language ?

How about namespaces ?

Thank you.
@dart-github-bot
Copy link
Collaborator

Summary: User requests adding public, private, and protected access modifiers to Dart, similar to other languages, and asks about namespace support. This revisits a five-year-old issue.

@dart-github-bot dart-github-bot added area-language Dart language related items (some items might be better tracked at github.com/dart-lang/language). triage-automation See https://github.com/dart-lang/ecosystem/tree/main/pkgs/sdk_triage_bot. type-question A question about expected behavior or functionality labels Jan 26, 2025
@lrhn
Copy link
Member

lrhn commented Jan 26, 2025 •
edited
Loading

any plans to finally add public, private and protected visibility modifiers to the language ?

No current plans, no.

No current plans for namespaces either.

If anything were to happen, it would likely be visible on the existing issues.

@lrhn lrhn closed this as not planned Won't fix, can't repro, duplicate, stale Jan 26, 2025
@lrhn lrhn added the closed-duplicate Closed in favor of an existing report label Jan 26, 2025
@lafrank
Copy link
Author

lafrank commented Jan 26, 2025

That's really disappoiting, thanks anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-language Dart language related items (some items might be better tracked at github.com/dart-lang/language). closed-duplicate Closed in favor of an existing report triage-automation See https://github.com/dart-lang/ecosystem/tree/main/pkgs/sdk_triage_bot. type-question A question about expected behavior or functionality
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lrhn @lafrank @dart-github-bot