Uh oh!
There was an error while loading. Please reload this page.
chore: Remove usage of paste crate - #20946
Conversation
coderfender
commented
Mar 14, 2026
TODO : Deprecate paste crate usage in |
d3b8705 to
3fd56d0Comparecoderfender
commented
Mar 14, 2026
@martin-g , ready for your review |
@comphead , I took the more laborious approach to remove paste crate and replace the macro defs with elaborated arguments than trying to find a new crate. Almost all other past crate usage is in tests / non critical path of code with one major usage in UDWF and Error macros |
3fd56d0 to
1e54eebComparecoderfender
commented
Mar 14, 2026
Fixed a typo |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
coderfender
commented
Mar 15, 2026
Thank you for the review @martin-g . Fixed the typo with |
6137d6f to
15c04c3Compare15c04c3 to
3b893edComparecomphead
commented
Mar 16, 2026
we would also need to rollback #20850 |
8b77322 to
b4812a8Comparecoderfender
commented
Mar 16, 2026
@comphead , thank you for the review. I was wondering if we could do it in a different PR but I believe we can do it in the current PR too. I just pushed a commit to unignore the rust warning in git wf. Please take a look whenever you get a chance |
13dad74 to
12dbdebComparepaste cratealamb
commented
Mar 16, 2026
this looks great -- thank you @coderfender and @martin-g. |
coderfender
commented
Mar 16, 2026
Thank you @alamb |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
comphead
left a comment
There was a problem hiding this comment.
Thanks @coderfender this is LGTM
PTAL on comments explaining why underscore variants are needed
coderfender
commented
Mar 16, 2026
Let me address the comments @comphead |
coderfender
commented
Mar 16, 2026
@comphead , done . I added the comments in macro def per your review |
comphead
commented
Mar 16, 2026
Thanks @coderfender and @martin-g |
Uh oh!
There was an error while loading. Please reload this page.
## 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 `Closesapache#123` indicates that this PR will close issue apache#123. --> - Closesapache#20853 ## Rationale for this change <!-- Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed. Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes. --> ## What changes are included in this PR? <!-- There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR. --> ## Are these changes tested? <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> ## Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> <!-- If there are any breaking changes to public APIs, please add the `api change` label. -->
Which issue does this PR close?
pastecrate from the project #20853Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?