missing_safety_doc accept uppercase "SAFETY"
          #13701
        
          
      
                
     Merged
            
            
          
  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.
  
    
  
    
changelog: [
missing_safety_doc]: accept uppercase "SAFETY"In Oxc's codebase, we try to draw attention as clearly as possible to the safety constraints of unsafe code by including an uppercase
# SAFETYdoc comment.Clippy's
missing_safety_doclint does not recognise "SAFETY" in upper case, so we also need to include#[expect(clippy::missing_safety_doc)]on every unsafe function, to avoid a false positive. Unfortunately this defeats the purpose of the lint, as if someone later removes the safety docs, the lint rule does not trigger.I don't know how common this style of documenting unsafe functions is, but I don't imagine also supporting
# SAFETYwould disturb other users who prefer# Safety.