- 
                Notifications
    You must be signed in to change notification settings 
- Fork 13.9k
Give spans to individual path segments in AST #40369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    
                
     Merged
            
            
          Conversation
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
    | cc @jseyfried | 
| @bors r+ | 
| 📌 Commit 7cfe20c has been approved by  | 
| Memory consumption:  | 
| 🔒 Merge conflict | 
| @nrc Can you use this to get rid of the span hacks in save-analysis? Or is it not enough? | 
| @bors: retry | 
    
  arielb1 
      pushed a commit
        to arielb1/rust
      that referenced
      this pull request
    
      Mar 9, 2017 
    
    
      
  
    
      
    
  
Give spans to individual path segments in AST And use these spans in path resolution diagnostics. The spans are spans of identifiers in segments, not whole segments. I'm not sure what spans are more useful in general, but identifier spans are a better fit for resolve errors. HIR still doesn't have spans. Fixes rust-lang#38927 (comment) rust-lang#38890 (comment) r? @nrc @eddyb
    
  alexcrichton 
      added a commit
        to alexcrichton/rust
      that referenced
      this pull request
    
      Mar 10, 2017 
    
    
      
  
    
      
    
  
Give spans to individual path segments in AST And use these spans in path resolution diagnostics. The spans are spans of identifiers in segments, not whole segments. I'm not sure what spans are more useful in general, but identifier spans are a better fit for resolve errors. HIR still doesn't have spans. Fixes rust-lang#38927 (comment) rust-lang#38890 (comment) r? @nrc @eddyb
    
  alexcrichton 
      pushed a commit
        to arielb1/rust
      that referenced
      this pull request
    
      Mar 10, 2017 
    
    
      
  
    
      
    
  
Give spans to individual path segments in AST And use these spans in path resolution diagnostics. The spans are spans of identifiers in segments, not whole segments. I'm not sure what spans are more useful in general, but identifier spans are a better fit for resolve errors. HIR still doesn't have spans. Fixes rust-lang#38927 (comment) rust-lang#38890 (comment) r? @nrc @eddyb
| @bors: r=eddyb | 
| 📌 Commit ffdcf74 has been approved by  | 
    
  alexcrichton 
      added a commit
        to alexcrichton/rust
      that referenced
      this pull request
    
      Mar 10, 2017 
    
    
      
  
    
      
    
  
Give spans to individual path segments in AST And use these spans in path resolution diagnostics. The spans are spans of identifiers in segments, not whole segments. I'm not sure what spans are more useful in general, but identifier spans are a better fit for resolve errors. HIR still doesn't have spans. Fixes rust-lang#38927 (comment) rust-lang#38890 (comment) r? @nrc @eddyb
    
  bors 
      added a commit
      that referenced
      this pull request
    
      Mar 11, 2017 
    
    
      
  
    
      
    
  
Rollup of 38 pull requests - Successful merges: #39202, #39820, #39918, #39921, #40092, #40146, #40199, #40225, #40239, #40257, #40259, #40261, #40277, #40278, #40287, #40297, #40311, #40315, #40319, #40324, #40336, #40340, #40344, #40345, #40367, #40369, #40372, #40373, #40379, #40385, #40386, #40389, #40400, #40404, #40410, #40422, #40423, #40424 - Failed merges: #40220, #40329, #40426
    
  bors 
      added a commit
      that referenced
      this pull request
    
      Mar 11, 2017 
    
    
      
  
    
      
    
  
Rollup of 38 pull requests - Successful merges: #39202, #39820, #39918, #39921, #40092, #40146, #40199, #40225, #40239, #40257, #40259, #40261, #40277, #40278, #40287, #40297, #40311, #40315, #40319, #40324, #40336, #40340, #40344, #40345, #40367, #40369, #40372, #40373, #40379, #40385, #40386, #40389, #40400, #40404, #40410, #40422, #40423, #40424 - Failed merges: #40220, #40329, #40426
| ⌛ Testing commit ffdcf74 with merge ef7bbdd... | 
    
  frewsxcv 
      added a commit
        to frewsxcv/rust
      that referenced
      this pull request
    
      Mar 12, 2017 
    
    
      
  
    
      
    
  
Give spans to individual path segments in AST And use these spans in path resolution diagnostics. The spans are spans of identifiers in segments, not whole segments. I'm not sure what spans are more useful in general, but identifier spans are a better fit for resolve errors. HIR still doesn't have spans. Fixes rust-lang#38927 (comment) rust-lang#38890 (comment) r? @nrc @eddyb
| @bors retry | 
| @eddyb some of them, but not all. | 
      
  
  Closed
  
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
And use these spans in path resolution diagnostics.
The spans are spans of identifiers in segments, not whole segments. I'm not sure what spans are more useful in general, but identifier spans are a better fit for resolve errors.
HIR still doesn't have spans.
Fixes #38927 (comment) #38890 (comment)
r? @nrc @eddyb