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.

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

Make proposal for optional argument names #1996

Closed
jonmeow opened this issue Aug 11, 2022 · 7 comments
Closed

Make proposal for optional argument names #1996

jonmeow opened this issue Aug 11, 2022 · 7 comments
Assignees
@matthew-russo
Labels
long term Issues expected to take over 90 days to resolve.

Comments

@jonmeow
Copy link
Contributor

jonmeow commented Aug 11, 2022

Unused argument names (e.g., fn Foo(unused arg: i32)) were the topic of leads question #476. The question was resolved, and the comment #476 (comment) has details.

Because the question was asked independent of a proposal, a standard proposal is still needed for evolution review, essentially translating the issue into a proposed solution with rationale, alternatives considered, etc. This issue is to track the proposal need.
@jonmeow jonmeow mentioned this issue Aug 11, 2022
Closed
@chandlerc chandlerc added the good first issue Possibly a good first issue for newcomers label Aug 12, 2022
@matthew-russo
Copy link
Contributor

I'd like to pick this up.

@matthew-russo matthew-russo mentioned this issue Aug 13, 2022
Merged
zygoloid added a commit that referenced this issue Sep 21, 2022
@matthew-russo @geoffromer @zygoloid
Unused Pattern Bindings (Unused Function Parameters) (#2022)
b464a0a 
This proposal specifies how unused pattern bindings are written in the Carbon programming language. This is a more general problem statement of "how do users specify unused function parameters" as function parameter declarations are a more specific form of pattern

Related issue #1996

Co-authored-by: Geoff Romer <[email protected]>
Co-authored-by: Richard Smith <[email protected]>
@github-actions
Copy link

We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please comment or remove the inactive label. The long term label can also be added for issues which are expected to take time.
This issue is labeled inactive because the last activity was over 90 days ago.

@github-actions github-actions bot added the inactive Issues and PRs which have been inactive for at least 90 days. label Nov 14, 2022
@josh11b josh11b added long term Issues expected to take over 90 days to resolve. and removed inactive Issues and PRs which have been inactive for at least 90 days. labels Dec 21, 2022
@rajeck1234
Copy link

can i fix this issue

@nikhil061102
Copy link

If no one is working on this issue, can it be assigned to me. I am new to the world of open source contribution and is very excited to start. This will also be a good start for me for GSoC 2023
Thank You

@jonmeow jonmeow removed the good first issue Possibly a good first issue for newcomers label Mar 13, 2023
@jonmeow
Copy link
Contributor Author

jonmeow commented Mar 13, 2023

This was fixed by #2022, I think we just missed closing it. (Thanks Matthew!)

@jonmeow jonmeow closed this as completed Mar 13, 2023
@nikhil061102

This comment was marked as off-topic.

Sign in to view
@jonmeow

This comment was marked as off-topic.

Sign in to view
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@matthew-russo matthew-russo

Labels
long term Issues expected to take over 90 days to resolve.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@chandlerc @josh11b @matthew-russo @jonmeow @rajeck1234 @nikhil061102