Reference
Constructor - Span
Function reference for iced::widget::span.
Constructor - Span
Authoritative source: ref/doc/iced/widget/fn.span.html.
# Rustdoc summary
Creates a new Span of text with the provided content.
# Verified signature
rust
pub fn span<'a, Link, Font>(text: impl IntoFragment<'a>) -> Span<'a, Link, Font>
# When to use
Use this constructor/helper as the typed entrypoint for the widget or layout helper it creates.
# Why to use
It gives explicit widget construction with compile-time type checking and builder chaining.
# Example References
- ref/examples/changelog/src/main.rs
- ref/examples/tour/src/main.rs
# Inline Examples (from rustdoc)
rust
use iced::font; use iced::widget::{rich_text, span}; use iced::{color, never, Font}; #[derive(Debug, Clone)] enum Message { // ... } fn view(state: &State) -> Element<'_, Message> { rich_text![ span("I am red!").color(color!(0xff0000)), " ", span("And I am bold!").font(Font { weight: font::Weight::Bold, ..Font::default() }), ] .on_link_click(never) .size(20) .into() }
# Related
# Use this when...
- You want the canonical entrypoint for creating this widget/helper.
- You need concrete constructor arguments and builder chaining.
- You are wiring UI interactions into typed messages.
# Minimal example
rust
// Call this constructor in `view`, then map events to Message variants.
# How it works
Constructors return typed widget values. You configure behavior via builder methods and emit Message values for update to handle.
# Common patterns
rust
// Keep constructor calls close to their message mapping. // Prefer small helper functions for repeated widget setups.
# Gotchas / tips
- Re-check argument order in the verified signature on this page.
- Keep side effects out of
view; trigger them fromupdatewith Task. - Use the related family page when deciding between module/element APIs.