# \[Pre-RFC\] inherent methods from any crate

**URL:** <https://internals.rust-lang.org/t/pre-rfc-inherent-methods-from-any-crate/3821>\
**Category:** language design\
**Created:** [August 5, 2016, 9:54pm UTC](https://internals.rust-lang.org/t/pre-rfc-inherent-methods-from-any-crate/3821 "2016-08-05T21:54:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jethrogb](https://avatars.discourse-cdn.com/v4/letter/j/43a26b/32.png) [@jethrogb](https://internals.rust-lang.org/u/jethrogb)\
**Post date:** [August 5, 2016, 10:01pm UTC](https://internals.rust-lang.org/t/pre-rfc-inherent-methods-from-any-crate/3821/2 "2016-08-05T22:01:53Z")

</div>

You can kind of emulate this behavior currently with a crate-local trait.

I don’t see this being very useful unless you can also override the field privacy restrictions, see [Add an #[allow(ignore\_field\_privacy)] annotation](https://internals.rust-lang.org/t/add-an-allow-ignore-field-privacy-annotation/625) and [Extending existing functionality](https://internals.rust-lang.org/t/extending-existing-functionality/1289/9)

---

_[View the full topic](https://internals.rust-lang.org/t/pre-rfc-inherent-methods-from-any-crate/3821)._