# \[Pre-RFC\] Elvis/coalesce + ternary operator

**URL:** <https://internals.rust-lang.org/t/pre-rfc-elvis-coalesce-ternary-operator/8537>\
**Category:** language design\
**Created:** [October 10, 2018, 10:18pm UTC](https://internals.rust-lang.org/t/pre-rfc-elvis-coalesce-ternary-operator/8537 "2018-10-10T22:18:07Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![ExpHP](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/exphp/32/6208_2.png) [@ExpHP](https://internals.rust-lang.org/u/ExpHP)\
**Post date:** [October 11, 2018, 10:03pm UTC](https://internals.rust-lang.org/t/pre-rfc-elvis-coalesce-ternary-operator/8537/21 "2018-10-11T22:03:06Z")

</div>

> [@skysch](#):
>
> Wouldn’t the orphan rules prevent anybody from relying on other implementations in the first place?

I meant this can happen even _within_ a crate. `Into` is such an extremely vague and general purpose trait. A lot of people use `Into` in their own crates for their own random reasons. Some of these people might also want to use `or` on an overlapping set of types.

---

_[View the full topic](https://internals.rust-lang.org/t/pre-rfc-elvis-coalesce-ternary-operator/8537)._