Skip to content

Adjust wording in the 'Private named parameters' proposal #4561

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

Merged
merged 1 commit into from
Nov 7, 2025
+3 −3
Merged

Adjust wording in the 'Private named parameters' proposal #4561

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions accepted/future-releases/2509-private-named-parameters/feature-specification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -228,9 +228,9 @@ encapsulation.

The basic idea is simple. We let users use a private name in a named parameter
when the parameter also initializes or declares a field. The compiler removes
the `_` from the argument name but keeps it for the corresponding field. In
other words, we do exactly what users are doing by hand when they write an
initializer like:
the `_` from the argument name at call sites but keeps it for the corresponding
field. In other words, we do exactly what users are doing by hand when they
write an initializer like:

```dart
class House {
Expand Down