Wishlist: functions with keyword args, optional args, and/or variable-arity argument (varargs) lists
*[View all comments](https://triagebot.infra.rust-lang.org/gh-comments/rust-lang/rfcs/issues/323)* A portion of the community (and of the core team) sees one or more of the following features as important for programmer ergonomics: - keyword-based parameters (as opposed to position-based parameters), - optional parameters (where one provides a default value for them, usually in the parameter list), - variable-arity functions (which can be seen as a generalization or variation on optional parameters, depending on how you look at it). This issue is recording that we want to investigate designs for this, but not immediately. The main backwards compatibility concern is about premature commitment to library API's that would be simplified if one adds one or more of the above features. Nonetheless, We believe we can produce a reasonable 1.0 version of Rust without support for this. (This issue is also going to collect links to all of the useful RFC PR's and/or Rust issues that contain community discussion of these features.)
Posted by pnkfelix on Sep 25, 2014, 10:18 PM
Tags
Related issues
Raise real-world problems, find people facing the same issue, and discuss solutions.9,000 issues0 comments
support (Sysadmin)
Support connecting to remote devcontainers (devcontainer on remote host)
Option to use Waffle menu or links displayed normally
I also attempted to package ROCM on musl.
But why is there no such pushback agains linux kernel?
OpenCode Support
Upcoming changes to the tado° API
Allow Mac users to use Apple native containerization
Support for the Containerization Framework on macOS
Wishlist: functions with keyword args, optional args, and/or variable-arity argument (varargs) lists
*[View all comments](https://triagebot.infra.rust-lang.org/gh-comments/rust-lang/rfcs/issues/323)* A portion of the community (and of the core team) sees one or more of the following features as important for programmer ergonomics: - keyword-based parameters (as opposed to position-based parameters), - optional parameters (where one provides a default value for them, usually in the parameter list), - variable-arity functions (which can be seen as a generalization or variation on optional parameters, depending on how you look at it). This issue is recording that we want to investigate designs for this, but not immediately. The main backwards compatibility concern is about premature commitment to library API's that would be simplified if one adds one or more of the above features. Nonetheless, We believe we can produce a reasonable 1.0 version of Rust without support for this. (This issue is also going to collect links to all of the useful RFC PR's and/or Rust issues that contain community discussion of these features.)
Comments (0)
No comments yet. Start the discussion.