HTHou opened a new pull request, #3637: URL: https://github.com/apache/thrift/pull/3637
## Summary Remove the Rust compiler target deprecation warning now that Rust maintenance has resumed. Dedicated CI, cross-tests, and crate publishing have been restored, and the Rust binding has received ongoing maintenance. This follows the latest discussion in [THRIFT-5917](https://issues.apache.org/jira/browse/THRIFT-5917). ## User impact Running the compiler with `--gen rs` no longer emits an outdated deprecation warning on stderr. Generated Rust code is unchanged. ## Validation - Built `thrift-compiler` from the current source with CMake. - Generated Rust code from `compiler/cpp/test/compiler/Single.thrift`; stderr was empty. - Compared generated output before and after the change; the SHA-256 hashes were identical. - `git diff --check` passed. - The changed region passed `clang-format` 17. - `make style` could not complete on macOS because the target uses GNU `find -printf`, which BSD `find` does not support. Generated-by: OpenAI Codex (GPT-5) <!-- Explain the changes in the pull request below: --> <!-- We recommend you review the checklist/tips before submitting a pull request. --> - [x] Did you create an [Apache Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) ticket? ([Request account here](https://selfserve.apache.org/jira-account.html), not required for trivial changes) - [x] If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"? - [x] Did you squash your changes to a single commit? (not required, but preferred) - [x] Did you do your best to avoid breaking changes? If one was needed, did you label the Jira ticket with "Breaking-Change"? - [ ] If your change does not involve any code, include `[skip ci]` anywhere in the commit message to free up build resources. <!-- The Contributing Guide at: https://github.com/apache/thrift/blob/master/CONTRIBUTING.md has more details and tips for committing properly. --> -- 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]
