about summary refs log tree commit diff
path: root/src/librustc_save_analysis/span_utils.rs
AgeCommit message (Collapse)AuthorLines
2018-12-25Remove licensesMark Rousskov-10/+0
2018-11-14save-analysis: be even more aggressive about ignorning macro-generated defsNick Cameron-5/+1
2018-10-26save-analysis: remove hacky, unnecessary code now that we have spans for ↵Nick Cameron-173/+11
every ident
2018-09-28Also remap absolute source names in save-analysisIgor Matuszewski-5/+12
2018-09-28Emit used rustc invocation in the save-analysis fileIgor Matuszewski-5/+8
2018-09-03A few cleanups and minor improvements to save_analysisljedrz-5/+2
2018-08-30Format codeEsteban Küber-2/+1
2018-08-19mv codemap() source_map()Donato Sciarra-3/+3
2018-08-19mv filemap source_fileDonato Sciarra-1/+1
2018-08-06Account for --remap-path-prefix in save-analysisIgor Matuszewski-4/+2
2018-04-12AST/HIR: Merge field access expressions for named and numeric fieldsVadim Petrochenkov-4/+0
2018-02-16save-analysis: power through bracket mis-countsNick Cameron-12/+14
Closes #47981 This is pretty unsatisfying since it is working around a span bug. However, I can't track down the span bug and it could be in the parser, proc macro expansion, the user macro, or Syn (or any other library that can manipulate spans). Given that user code can cause this error, I think we need to be more robust here.
2017-12-14Use PathBuf instead of String where applicableOliver Schneider-11/+9
2017-11-08save-analysis: run rustfmtNick Cameron-14/+24
2017-11-06save-analysis: fix bugs in method chainsNick Cameron-42/+1
Use the span we save in the PathSegment for a method call, rather than searching for it in the text. Fixes https://github.com/nrc/rls-analysis/issues/111
2017-08-30Make fields of `Span` privateVadim Petrochenkov-2/+2
2017-08-15use field init shorthand EVERYWHEREZack M. Davis-1/+1
Like #43008 (f668999), but _much more aggressive_.
2017-08-14save-analysis: Remove path span extraction methods from SpanUtilskennytm-85/+0
Use the `span` field in PathSegment and TyParam instead. Fix #43796. Close #41478.
2017-08-01review changesNick Cameron-4/+5
2017-07-28save-anlaysis: fix filter_generatedNick Cameron-1/+1
2017-06-16Remove intermediate forms and some other refactoringNick Cameron-91/+38
2017-03-29Refactor how spans are combined in the parser.Jeffrey Seyfried-2/+2
2017-03-29Merge `ExpnId` and `SyntaxContext`.Jeffrey Seyfried-2/+1
2017-03-03Integrate `TokenStream`.Jeffrey Seyfried-1/+1
2017-02-28Add `syntax::ext::tt::quoted::{TokenTree, ..}` and remove ↵Jeffrey Seyfried-3/+3
`tokenstream::TokenTree::Sequence`.
2017-02-28rustc_save_analysis: don't pollute the codemap with fake files.Eduard Burtescu-51/+16
2017-01-17Introduce `string_reader.parse_all_token_trees()`.Jeffrey Seyfried-5/+5
2017-01-17Give the `StringReader` a `sess: &ParseSess`.Jeffrey Seyfried-2/+1
2016-12-22rebasing fixNick Cameron-1/+1
2016-12-22signature info for other items (mods, fns, methods, etc.)Nick Cameron-5/+8
2016-12-22save-analysis: add `Signature` info to structsNick Cameron-2/+43
2016-11-20Move `syntax::util::interner` -> `syntax::symbol`, cleanup.Jeffrey Seyfried-1/+2
2016-11-18save-analysis: handle << and >> operators inside [] in typesNick Cameron-14/+42
Fixes #37700
2016-10-31Changed most vec! invocations to use square bracesiirelu-2/+2
Most of the Rust community agrees that the vec! macro is clearer when called using square brackets [] instead of regular brackets (). Most of these ocurrences are from before macros allowed using different types of brackets. There is one left unchanged in a pretty-print test, as the pretty printer still wants it to have regular brackets.
2016-10-05Rename Parser::last_span as prev_span.Nicholas Nethercote-5/+5
This is a [breaking-change] for libsyntax.
2016-06-23Move errors from libsyntax to its own crateJonathan Turner-1/+1
2016-06-16Add an abs_path member to FileMap, use it when writing debug info.Ted Mielczarek-1/+1
When items are inlined from extern crates, the filename in the debug info is taken from the FileMap that's serialized in the rlib metadata. Currently this is just FileMap.name, which is whatever path is passed to rustc. Since libcore and libstd are built by invoking rustc with relative paths, they wind up with relative paths in the rlib, and when linked into a binary the debug info uses relative paths for the names, but since the compilation directory for the final binary, tools trying to read source filenames will wind up with bad paths. We noticed this in Firefox with source filenames from libcore/libstd having bad paths. This change stores an absolute path in FileMap.abs_path, and uses that if available for writing debug info. This is not going to magically make debuggers able to find the source, but it will at least provide sensible paths.
2016-05-03save-analysis: use a decoupled representation for dumped dataAdolfo Ochagavía-21/+2
Closes #33348
2016-04-20debugging, misc fixesNick Cameron-0/+2
2016-03-31librustc_save_analysis: use bug!(), span_bug!()Benjamin Herr-13/+13
2016-03-27rustc_trans: move save to librustc_save_analysis.Eduard Burtescu-0/+461