summary refs log tree commit diff
path: root/src/librustc_resolve/lib.rs
AgeCommit message (Collapse)AuthorLines
2018-03-26Auto merge of #49101 - mark-i-m:stabilize_i128, r=nagisabors-12/+1
Stabilize 128-bit integers :tada: cc #35118 EDIT: This should be merged only after the following have been merged: - [x] https://github.com/rust-lang-nursery/compiler-builtins/pull/236 - [x] https://github.com/rust-lang/book/pull/1230
2018-03-26remove unneeded importMark Mansi-1/+1
2018-03-26Stabilize i128_typeMark Mansi-11/+0
2018-03-26Rollup merge of #48693 - vorner:doc-name-resolution, r=petrochenkovTim Neumann-3/+58
Some comments and documentation for name resolution crate Hello I'm trying to get a grasp of how the name resolution crate works, as part of helping with https://github.com/rust-lang-nursery/rustc-guide/issues/16. Not that I'd be succeeding much, but as I was reading the code, I started to put some notes into it, to help me understand. I guess I didn't get very far yet, but I'd like to share what I have, in case it might be useful for someone else. I hope these are correct (even if incomplete), but I'll be glad for a fast check in case I put something misleading there.
2018-03-24fixup! Some comments and documentation for name resolution crateMichal 'vorner' Vaner-7/+23
2018-03-18Initial implementation of RFC 2151, Raw IdentifiersLymia Aluysia-1/+1
2018-03-17Rename `Span::empty` to `Span::shrink_to_lo`, add `Span::shrink_to_hi`Vadim Petrochenkov-3/+3
2018-03-17AST: Keep distinction between `path` and `::path` in imports and visibilitiesVadim Petrochenkov-8/+11
Add the root segment for name resolution purposes only
2018-03-14Some tweaks to "type parameters from outer function" diagnosticEsteban Küber-12/+18
Follow up to #47574.
2018-03-12Some comments and documentation for name resolution crateMichal 'vorner' Vaner-3/+42
2018-03-08Update "type parameters from outer function" error messagesBasile Desloges-6/+122
2018-03-05Turn features() into a query.Michael Woerister-3/+3
2018-03-02Replace Rc with Lrc for shared dataJohn Kåre Alsaker-3/+3
2018-02-28Remove E0245; improve E0404 explanationMark Mansi-7/+9
2018-02-24Implement multiple patterns with `|` in `if let` and `while let`Vadim Petrochenkov-12/+24
2018-02-23Auto merge of #47799 - topecongiro:fix-span-of-visibility, r=petrochenkovbors-5/+7
Fix span of visibility This PR 1. adds a closing parenthesis to the span of `Visibility::Crate` (e.g. `pub(crate)`). The current span only covers `pub(crate`. 2. adds a `span` field to `Visibility::Restricted`. This span covers the entire visibility expression (e.g. `pub (in self)`). Currently all we can have is a span for `Path`. This PR is motivated by the bug found in rustfmt (https://github.com/rust-lang-nursery/rustfmt/issues/2398). The first change is a strict improvement IMHO. The second change may not be desirable, as it adds a field which is currently not used by the compiler.
2018-02-20stage0 cfg cleanupMark Simulacrum-1/+0
2018-02-17fix more typos found by codespell.Matthias Krüger-1/+1
2018-02-18Change ast::Visibility to Spanned typeSeiichi Uchida-5/+7
2018-02-18Add a span field to Visibility::RestrictedSeiichi Uchida-1/+1
This span covers the whole visibility expression: e.g. `pub (in path)`.
2018-01-28use correct casing for rename suggestionsAndy Russell-3/+9
If the original name is uppercase, use camel case. Otherwise, use snake case.
2018-01-28Auto merge of #47767 - estebank:as-suggestion, r=petrochenkovbors-3/+9
Correctly format `extern crate` conflict resolution help Closes #45799. Follow up to @Cldfire's #45820. If the `extern` statement that will have a suggestion ends on a `;`, synthesize a new span that doesn't include it.
2018-01-27end_point handling multibyte characters correctly.David Wood-2/+2
2018-01-26Instead of modifying the item's span synthesize itEsteban Küber-1/+7
2018-01-25Correctly format `extern crate` conflict resolution helpCldfire-2/+2
2018-01-25Rollup merge of #47705 - pietroalbini:fix-47673, r=petrochenkovAlex Crichton-5/+5
Fix ICE when use trees have multiple empty nested groups The issue was caused by an oversight of mine in the original use_nested_groups PR, where different paths were resolved with the same `NodeId` in some cases (such as in `use {{}, {}};`). Fixes #47673 r? @petrochenkov
2018-01-25Rollup merge of #47502 - petrochenkov:label, r=eddybAlex Crichton-7/+7
AST/HIR: Add a separate structure for labels
2018-01-24Fix ICE when use trees have multiple empty nested groupsPietro Albini-5/+5
2018-01-22AST/HIR: Add a separate structure for labelsVadim Petrochenkov-7/+7
2018-01-22Review fixesManish Goregaokar-2/+2
2018-01-22Store a list of local macros on the resolver; use for resolving intra-doc ↵Manish Goregaokar-0/+2
macro links
2018-01-22Fix tidyManish Goregaokar-1/+2
2018-01-22Handle relative pathsManish Goregaokar-28/+36
2018-01-22Make resolve_hir_path and resolve_str_path fallibleManish Goregaokar-10/+60
2018-01-21Rollup merge of #47512 - GuillaumeGomez:e0659, r=petrochenkovGuillaume Gomez-1/+1
Add E0659 for ambiguous names Still on the tracks of the "no error without error code" road.
2018-01-21Auto merge of #47116 - estebank:non-accessible-ctor, r=petrochenkovbors-18/+30
Tweaks to invalid ctor messages - Do not suggest using a constructor that isn't accessible - Suggest the appropriate syntax (`()`/`{}` as appropriate) - Add note when trying to use `Self` as a ctor CC #22488, fix #47085.
2018-01-20Fix tests by keepeing needed suggestionsEsteban Küber-1/+9
2018-01-18in which the unused-parens lint comes to cover function and method argsZack M. Davis-1/+1
Resolves #46137.
2018-01-18Add E0659 for ambiguous namesGuillaume Gomez-1/+1
2018-01-18Rollup merge of #47498 - dominikWin:missing-module-name, r=petrochenkovkennytm-4/+4
Make non-found module name optional No longer uses a magic string for missing or root module.
2018-01-16Make non-found module name optionalDominik Winecki-4/+4
No longer uses a magic string for missing or root module.
2018-01-15Review comments: remove enum suggestionEsteban Küber-25/+3
2018-01-15Further tweaks to the outputEsteban Küber-19/+16
- Properly address Variant Ctors - Show signature if span of trait method without `self` is not available
2018-01-15Reexport -> re-export in error messagesCarol (Nichols || Goulding)-1/+1
2018-01-15address review commentsEsteban Küber-13/+10
2018-01-15Add note when trying to use `Self` as a ctorEsteban Küber-1/+5
2018-01-15Readd suggestion in enum variants with incorrect argsEsteban Küber-0/+12
2018-01-15Suggest the correct syntax for different struct typesEsteban Küber-12/+22
2018-01-15Hide suggestion to use struct ctor when it is not visibleEsteban Küber-5/+11
2018-01-13Remove `impl Foo for ..` in favor of `auto trait Foo`leonardo.yvens-6/+0
No longer parse it. Remove AutoTrait variant from AST and HIR. Remove backwards compatibility lint. Remove coherence checks, they make no sense for the new syntax. Remove from rustdoc.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-27 14:27:22 +0000