# Delegate trait implementations with procedural macros

**URL:** https://internals.rust-lang.org/t/delegate-trait-implementations-with-procedural-macros/6357
**Category:** language design
**Created:** [December 9, 2017, 5:08pm UTC](https://internals.rust-lang.org/t/delegate-trait-implementations-with-procedural-macros/6357 "2017-12-09T17:08:59Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![scottmcm](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/scottmcm/32/2355_2.png) [@scottmcm](https://internals.rust-lang.org/u/scottmcm)
#### Post date: [December 10, 2017, 9:35am UTC](https://internals.rust-lang.org/t/delegate-trait-implementations-with-procedural-macros/6357/2 "2017-12-10T09:35:30Z")

</div>

I think there’s appetite for full, in-language syntax for this. It’s “an important problem the lang team would like to tackle” per

[https://github.com/rust-lang/rfcs/pull/1406](https://github.com/rust-lang/rfcs/pull/1406)

See also [this newer delegation thread](https://internals.rust-lang.org/t/3-weeks-to-delegation-please-help/5742?u=scottmcm) that was working on a new design.

---

_[View the full topic](https://internals.rust-lang.org/t/delegate-trait-implementations-with-procedural-macros/6357)._