|tagger||Natalie Weizenbaum <email@example.com>||Wed Sep 02 13:32:56 2015 -0700|
Add SourceLocationMixin and SourceLocationBase.
|author||Natalie Weizenbaum <firstname.lastname@example.org>||Wed Sep 02 13:32:02 2015 -0700|
|committer||Natalie Weizenbaum <email@example.com>||Wed Sep 02 13:32:02 2015 -0700|
Add SourceLocationMixin and SourceLocationBase. This allows FileLocation to avoid extending SourceLocation at all, which avoids unused line, column, and sourceUrl fields. This produces a speed improvement of approximately 5% in the YAML parser, and will likely do more in code that uses locations more heavily relative to spans. Rfirstname.lastname@example.org Review URL: https://codereview.chromium.org//1307123004 .
source_span is a library for tracking locations in source code. It's designed to provide a standard representation for source code locations and spans so that disparate packages can easily pass them among one another, and to make it easy to generate human-friendly messages associated with a given piece of code.
The most commonly-used class is the package's namesake,
SourceSpan. It represents a span of characters in some source file, and is often attached to an object that has been parsed to indicate where it was parsed from. It provides access to the text of the span via
SourceSpan.text and can be used to produce human-friendly messages using
When parsing code from a file,
SourceFile is useful. Not only does it provide an efficient means of computing line and column numbers,
SourceFile.span() returns special
FileSpans that are able to provide more context for their error messages.