xanderbailey opened a new pull request, #2542:
URL: https://github.com/apache/iceberg-rust/pull/2542

   https://github.com/apache/iceberg-rust/pull/2525 introduced public-api files 
but after writing https://github.com/apache/iceberg-rust/pull/2541/changes I 
realised this might be a little too noisy since it incudes all auto-trait like 
`Send` `Sync` etc.
   
   Options are:
   * -s Omits blanket impls (From<T>, Into<U>, Borrow, Any, etc.)
   * -ss Also omits auto-trait impls (Send, Sync, Unpin, Freeze, etc.)
   * -sss Also omits auto-derived impls (Clone, Debug, Eq)
   
   
   ## Which issue does this PR close?
   
   <!--
   We generally require a GitHub issue to be filed for all bug fixes and 
enhancements and this helps us generate change logs for our releases. You can 
link an issue to this PR using the GitHub syntax. For example `Closes #123` 
indicates that this PR will close issue #123.
   -->
   
   - Closes #.
   
   ## What changes are included in this PR?
   
   Pass -sss to cargo-public-api to reduce noise in public-api.txt files. This 
removes ~13k lines of auto-generated blanket impls, auto-trait impls, and 
auto-derived impls that obscure actual API surface changes in diffs.
   
   <!--
   Provide a summary of the modifications in this PR. List the main changes 
such as new features, bug fixes, refactoring, or any other updates.
   -->
   
   ## Are these changes tested?
   
   <!--
   Specify what test covers (unit test, integration test, etc.).
   
   If tests are not included in your PR, please explain why (for example, are 
they covered by existing tests)?
   -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to