doc: replace allocUnsafe with alloc in examples #60477
                
     Open
            
            
          
      
        
          +71
        
        
          −71
        
        
          
        
      
    
  
  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.
  
    
  
    
Do not needlessly promote
allocUnsafe.Dates back to #4682
While the intention was to make
allocUnsafea code replacement for Buffer constructor, it has also been to let users useBuffer.allocby default and/or when they are not sure, and optimize withallocUnsafeonly when needed and when they ensured that nothing gets leaked (which often requires extra actions e.g. error handling or guards against race conditions)Most documentation methods should use
Buffer.allocinstead ofBuffer.allocUnsafeby default in examplesThis aligns documentation accents internally with the wording in this intent:
node/doc/api/buffer.md
Lines 5066 to 5067 in dec0213
And https://nodejs.org/docs/latest/api/buffer.html#bufferfrom-bufferalloc-and-bufferallocunsafe