mirror of
https://github.com/zed-industries/zed.git
synced 2025-01-27 12:54:42 +00:00
Add short top-level description of a crate
This commit is contained in:
parent
6144ee1b5d
commit
ebe2c3658c
1 changed files with 8 additions and 3 deletions
|
@ -1,7 +1,12 @@
|
|||
//! The `language` crate provides... ???
|
||||
|
||||
#![warn(missing_docs)]
|
||||
|
||||
//! The `language` crate provides a large chunk of Zed's language-related
|
||||
//! features (the other big contributors being project and lsp crates that revolve around LSP features).
|
||||
//! Namely, this crate:
|
||||
//! - Provides [`Language`], [`Grammar`] and [`LanguageRegistry`] types that
|
||||
//! use Tree-sitter to provide syntax highlighting to the editor; note though that `language` doesn't perform the highlighting by itself. It only maps ranges in a buffer to colors. Treesitter is also used for buffer outlines (lists of symbols in a buffer)
|
||||
//! - Exposes [`LanguageConfig`] that describes how constructs (like brackets or line comments) should be handled by the editor for a source file of a particular language.
|
||||
//!
|
||||
//! Notably we do *not* assign a single language to a single file; in real world a single file can consist of multiple programming languages - HTML is a good example of that - and `language` crate tends to reflect that status quo in it's API.
|
||||
mod buffer;
|
||||
mod diagnostic_set;
|
||||
mod highlight_map;
|
||||
|
|
Loading…
Reference in a new issue