#[repr(C)]pub struct NumberLiteralTypeAnnotation<'gc> {
pub metadata: NodeMetadata<'gc>,
pub value: Cell<f64>,
pub raw: Cell<NodeLabel>,
}Expand description
The NumberLiteralTypeAnnotation AST node.
Fields§
§metadata: NodeMetadata<'gc>Source range, debug location, paren count, and node id.
value: Cell<f64>ESTree value property.
raw: Cell<NodeLabel>ESTree raw property.
Implementations§
Source§impl<'gc> NumberLiteralTypeAnnotation<'gc>
impl<'gc> NumberLiteralTypeAnnotation<'gc>
Sourcepub fn new(metadata: NodeMetadata<'gc>, value: f64, raw: NodeLabel) -> Self
pub fn new(metadata: NodeMetadata<'gc>, value: f64, raw: NodeLabel) -> Self
Build NumberLiteralTypeAnnotation from its metadata and ESTree.def
fields.
Sourcepub fn raw_str<'a>(&self, gc: &'a GCLock<'_, '_>) -> &'a str
pub fn raw_str<'a>(&self, gc: &'a GCLock<'_, '_>) -> &'a str
The raw label as UTF-8 text.
Label fields hold identifier names, operators, keyword-like kinds and raw source spans. An identifier cannot contain an unpaired surrogate — the lexer rejects one with a dedicated diagnostic — and the remaining labels are literal source text, so in practice the bytes are already valid UTF-8 and this borrows them directly, allocating nothing.
A label that is nevertheless unrepresentable, which realistically means
a hand-built AST rather than a parsed one, has each unpaired surrogate
rendered as a single U+FFFD instead of being reported. Only an unpaired
surrogate is affected: a WTF-8 surrogate pair is folded back into the
character it encodes, so a "😀" label comes out intact.
Use GCLock::bytes for the exact
bytes, or
GCLock::try_bytes_str to
detect the substitution. The returned &str borrows from gc, not from
self.