Struct Span 

pub struct Span {
    pub start: Position,
    pub end: Position,
}

Source code span (line and column information)

Fields

start: Position

Starting position

end: Position

Ending position

Implementations

impl Span

pub fn new(start: Position, end: Position) -> Self

Create a new span

pub fn from_node(node: &Node<'_>) -> Self

Create a span from a tree-sitter node’s real row and column.

This is what a plugin should call when it has the node in hand, which is nearly always. It takes the node by reference to match the private extension traits that the cpp, kotlin and sql plugins had each already written for themselves, which this replaces.

Prefer it over Span::from_bytes without exception: the two return the same type and look equally correct at a call site, but from_bytes stores byte offsets in the line and column fields, so anything built from it reports line 1 with a nonsense column.

pub fn from_bytes(start: usize, end: usize) -> Self

👎Deprecated since 31.0.0:

builds a line-1 span with the byte offset in the column; use Span::from_node, or LineIndex::span when only offsets are available

Create a span from raw byte offsets, WITHOUT resolving them to a line and column.

This is lossy and the loss is invisible: it stores the offsets in the line/column fields and sets line: 0, which every display path renders as line 1. A Span built this way is indistinguishable by type from a correct one, which is how ten language plugins came to report every declaration at line 1 with the byte offset as the column, found by audit on 2026-08-22.

Use Span::from_node when a node is available. This remains only for call sites that genuinely hold nothing but offsets, such as a scope or call-context tuple, and whose spans are not surfaced as symbol positions.

Deprecated so the rule is enforced by the compiler rather than by this comment. Every language plugin that used to build declaration spans this way reported line 1 with a byte offset in the column (issue #725), and a new plugin reaching for it would reintroduce that. There are now ZERO call sites: do not add #[allow(deprecated)] to create one. Use Span::from_node when a node is in hand, or LineIndex::span when only byte offsets are.

Trait Implementations

impl Clone for Span

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Copy for Span

impl Debug for Span

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for Span

fn default() -> Self

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for Span

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Eq for Span

impl Hash for Span

fn hash<__H: Hasher>(&self, state: &mut __H)

Feeds this value into the given Hasher.

fn hash_slice<H>(data: &[Self], state: &mut H)

where H: Hasher, Self: Sized,

Feeds a slice of this type into the given Hasher.

impl PartialEq for Span

fn eq(&self, other: &Self) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl Serialize for Span

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl StructuralPartialEq for Span