- 
                Notifications
    You must be signed in to change notification settings 
- Fork 13.9k
Rollup of 15 pull requests #146665
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
          
     Closed
      
      
    
                
     Closed
            
            Rollup of 15 pull requests #146665
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
    
  
  
    
    Co-authored-by: Travis Cross <[email protected]>
``` error: unexpected `...` --> $DIR/varargs-in-closure-isnt-supported.rs:5:20 | LL | let mut lol = |...| (); | ^^^ not a valid pattern | = note: C-variadic type `...` is not allowed here ```
All of the tier 3 targets in the list now link dynamically by default (except mips64el-unknown-linux-muslabi64, I overlooked that one). Adjust the list of targets expected to link statically accordingly. Signed-off-by: Jens Reidel <[email protected]>
When writing something like the expression `|_: ...| {}`, we now detect the `...` during parsing explicitly instead of relying on the detection in `parse_ty_common` so that we don't talk about "nested `...` are not supported".
```
error: unexpected `...`
  --> $DIR/no-closure.rs:6:35
   |
LL | const F: extern "C" fn(...) = |_: ...| {};
   |                                   ^^^
   |
   = note: only `extern "C"` and `extern "C-unwind"` functions may have a C variable argument list
```
    update Readme add info about githooks and bootstrap.toml add info about config and remove linting specific files add link to rustc-dev-guide
| Pre-trying a few jobs in parallel. @bors try jobs=test-various,dist-various-1,aarch64-apple,i686-msvc-1,i686-msvc-2 | 
      
        
              This comment has been minimized.
        
        
      
    
  This comment has been minimized.
    
  rust-bors bot
      added a commit
      that referenced
      this pull request
    
      Sep 17, 2025 
    
    
      
  
    
      
    
  
Rollup of 15 pull requests try-job: test-various try-job: dist-various-1 try-job: aarch64-apple try-job: i686-msvc-1 try-job: i686-msvc-2
| The job  Click to see the possible cause of the failure (guessed by this bot) | 
| The job  Click to see the possible cause of the failure (guessed by this bot) | 
| 💔 Test for 5d12a45 failed: CI. Failed jobs: 
 | 
| I'll re-rollup without the conflict. | 
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      Labels
      
    A-attributes
  Area: Attributes (`#[…]`, `#![…]`) 
  
    A-CI
  Area: Our Github Actions CI 
  
    A-LLVM
  Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. 
  
    A-run-make
  Area: port run-make Makefiles to rmake.rs 
  
    A-rustc-dev-guide
  Area: rustc-dev-guide 
  
    A-testsuite
  Area: The testsuite used to check the correctness of rustc 
  
    A-tidy
  Area: The tidy tool 
  
    O-apple
  Operating system: Apple (macOS, iOS, tvOS, visionOS, watchOS) 
  
    rollup
  A PR which is a rollup 
  
    S-waiting-on-bors
  Status: Waiting on bors to run and complete tests. Bors will change the label on completion. 
  
    T-bootstrap
  Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) 
  
    T-clippy
  Relevant to the Clippy team. 
  
    T-compiler
  Relevant to the compiler team, which will review and decide on the PR/issue. 
  
    T-infra
  Relevant to the infrastructure team, which will review and decide on the PR/issue. 
  
    T-libs
  Relevant to the library team, which will review and decide on the PR/issue. 
  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.
  
    
  
    
Successful merges:
btree_entry_insertfeature #144871 (Stabilizebtree_entry_insertfeature)has_significant_drop, it never encounters inference variables #145181 (remove FIXME block fromhas_significant_drop, it never encounters inference variables)super let#145838 (don't apply temporary lifetime extension rules to non-extendedsuper let)lastandcount#146410 (Iterator repeat: no infinite loop forlastandcount)Failed merges:
#[rustc_coherence_is_core]to thecrate_levelfile #146647 (Move#[rustc_coherence_is_core]to thecrate_levelfile)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup