# Pre-RFC: Disallow using assignment in a function call in Rust 2018 (disallow \`f(a=b)\`)

**URL:** https://internals.rust-lang.org/t/pre-rfc-disallow-using-assignment-in-a-function-call-in-rust-2018-disallow-f-a-b/7469
**Category:** language design
**Created:** [May 8, 2018, 9:39am UTC](https://internals.rust-lang.org/t/pre-rfc-disallow-using-assignment-in-a-function-call-in-rust-2018-disallow-f-a-b/7469 "2018-05-08T09:39:02Z")
**Posts on this page:** 1
**Showing post:** 29

<div class="post-metadata">

### Author: ![est31](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/est31/32/2551_2.png) [@est31](https://internals.rust-lang.org/u/est31)
#### Post date: [May 14, 2018, 3:30am UTC](https://internals.rust-lang.org/t/pre-rfc-disallow-using-assignment-in-a-function-call-in-rust-2018-disallow-f-a-b/7469/29 "2018-05-14T03:30:36Z")

</div>

I consider named arguments to be a bad idea for various reasons. So I don’t think we need this breaking change.

---

_[View the full topic](https://internals.rust-lang.org/t/pre-rfc-disallow-using-assignment-in-a-function-call-in-rust-2018-disallow-f-a-b/7469)._