# \[Pre-RFC\] named arguments

**URL:** <https://internals.rust-lang.org/t/pre-rfc-named-arguments/3831>\
**Category:** language design\
**Created:** [August 8, 2016, 9:57am UTC](https://internals.rust-lang.org/t/pre-rfc-named-arguments/3831 "2016-08-08T09:57:08Z")\
**Posts on this page:** 1\
**Showing post:** 234

<div class="post-metadata">

**Author:** ![crumblingstatue](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/crumblingstatue/32/202_2.png) [@crumblingstatue](https://internals.rust-lang.org/u/crumblingstatue)\
**Post date:** [April 8, 2017, 6:40am UTC](https://internals.rust-lang.org/t/pre-rfc-named-arguments/3831/234 "2017-04-08T06:40:44Z")

</div>

The problem with the struct based solutions is that they add API boilerplate.

Not only defining named arguments is more complicated than necessary, but the user also has to look up the definition for the fields struct to know what arguments the function accepts, instead of them being defined inline.

I’m strongly in favor of inline solutions.

---

_[View the full topic](https://internals.rust-lang.org/t/pre-rfc-named-arguments/3831)._
