Skip to content
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.

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

spec typo: change "keyword" to "named" #29464

Closed
danrubel opened this issue Apr 25, 2017 · 1 comment
Closed

spec typo: change "keyword" to "named" #29464

danrubel opened this issue Apr 25, 2017 · 1 comment
Labels
area-specification (deprecated) Deprecated: use area-language and a language- label.

Comments

@danrubel
Copy link

In the paragraph below from page 66 of the dart language spec, I believe "keyword" should be changed to "named"

"If T is malformed or if T is a type variable a dynamic error occurs. In
checked mode, if T or any of its superclasses is malbounded a dynamic error
occurs. Otherwise, if q is not defined or not accessible, a NoSuchMethodError
is thrown. If q has less than n positional parameters or more than n required
parameters, or if q lacks any of the keyword parameters {xn+1, . . . , xn+k} a
NoSuchMethodError is thrown"

@danrubel danrubel added the area-specification (deprecated) Deprecated: use area-language and a language- label. label Apr 25, 2017
@eernstg
Copy link
Member

eernstg commented Apr 25, 2017

I agree that keyword parameters should have been named parameters. The phrase keyword parameter occurs only once in the spec, it has never been added nor removed from the spec (and it was present in the version of the spec that was initially added to the repository on Oct 8 2013), and it all makes sense iff we make that change. ;-)

Here's a CL for that.

lrhn pushed a commit to dart-lang/language that referenced this issue Aug 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-specification (deprecated) Deprecated: use area-language and a language- label.
Projects
None yet
Development

No branches or pull requests

2 participants