laizy 39467cf4b1 gpui: Remove hand-written IntoElement impls for elements (#64864)
Custom elements previously had to hand-write an `IntoElement` impl that
just returned `self`. Replace that boilerplate with a blanket `impl<T:
Element> IntoElement for T`, and relax the `Element` supertrait bound
from `IntoElement` to `Sized`. Any type implementing `Element` is now
usable as a child element without extra code.

`AnyElement` overrides `into_any` to return `self`, so converting one
does not nest a boxed element inside another. To make that easy to
notice, the private `AnyElement::new` is renamed to
`new_please_call_into_any_to_avoid_double_box`.

Remove the now-redundant `IntoElement` impls across gpui and its
consumers.

## Testing

Manually test your changes; report results, mention platforms if
relevant.
How can reviewers test this easily? Include setup and steps.

## Self-review

- [x] I've reviewed my diff for quality, security, reliability, and
performance.
- [ ] UI changes follow the
[checklist](https://zed.dev/docs/development/ui-checklist).
- [ ] Tests cover the new or changed behavior.

Release Notes:

- [GPUI] (breaking) Added blanket impl for `IntoElement` trait with
`ElementType = Self` when `Self` implements `Element`.

---------

Co-authored-by: Amp <amp@ampcode.com>
2026-11-09 11:01:36 +00:00
…
…
2026-11-08 18:27:50 +00:00
…
…
2026-11-08 18:27:50 +00:00
2026-11-08 18:27:50 +00:00
…
2026-10-26 10:10:32 +00:00
…
…
…
…
…

Zed

Zed CI

Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.


Installation

On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).

Other platforms are not yet available:

Developing Zed

Contributing

See CONTRIBUTING.md for ways you can contribute to Zed.

Also... we're hiring! Check out our jobs page for open roles.

Licensing

Zed source code is licensed primarily under GPL-3.0-or-later, with Apache-2.0 components where marked.

License information for third party dependencies must be correctly provided for CI to pass.

We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:

  • Is it showing a no license specified error for a crate you've created? If so, add publish = false under [package] in your crate's Cargo.toml.
  • Is the error failed to satisfy license requirements for a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to the accepted array in script/licenses/zed-licenses.toml.
  • Is cargo-about unable to find the license for a dependency? If so, add a clarification field at the end of script/licenses/zed-licenses.toml, as specified in the cargo-about book.

Sponsorship

Zed is developed by Zed Industries, Inc., a for-profit company.

If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.

S
Description
No description provided
Readme 1.6 GiB
Languages
Rust 95.4%
JSON-with-Comments 2.4%
Python 0.8%
Inno Setup 0.3%
Tree-sitter Query 0.3%
Other 0.4%