blue-lang-syntax 0.0.47

//! blue's surface syntax.
//!
//! Blue is a general-purpose language whose surface is Ruby/Elixir-shaped
//! and whose **program is a tatara-lisp value**. This crate is the join:
//! it lexes blue source and parses it directly into `tatara_lisp::Sexp`.
//!
//! There is deliberately no private blue AST in between. Tenet 1 of
//! `theory/BLUE.md` is that blue source parses *to tatara-lisp*, and an
//! intermediate tree would make homoiconicity a conversion step rather
//! than an identity — the difference between blue's macro story working
//! and merely being asserted.
//!
//! ```
//! use blue_lang_syntax::parse_expr;
//! let form = parse_expr("user.greet(1)").unwrap();
//! assert_eq!(form.to_string(), "(greet user 1)");
//! ```

pub mod kigou;
pub mod lex;
pub mod parse;
pub mod yakugo;

pub use lex::{lex, LexError, Span, Token, TokenKind};
// Re-exported so a consumer walking blue trees does not have to depend on
// tatara-lisp directly just to name the node types blue emits.
pub use parse::{
    comments, is_reserved_word, parse_expr, parse_program, parse_program_in, parse_program_spanned,
    parse_program_spanned_with_depth, parse_program_tree, parse_program_tree_in,
    parse_program_tree_with_depth, parse_program_with_depth, Comment, Infix, ParseError,
    BLOCK_KEYWORDS, INFIX, LOWERED_ASSERT, LOWERED_CONCAT, LOWERED_MAP, MAX_EXPR_DEPTH,
    SURFACE_KEYWORDS,
};
// `Spanned`/`SpannedForm` alongside `Sexp` for the same reason `Sexp` is here:
// the parser's real output is the spanned tree, and a consumer that wants a
// position should not have to add a tatara-lisp dependency to name the node it
// got a span from.
pub use tatara_lisp::{Atom, Sexp, Spanned, SpannedForm};