Skip to content

[Docathon][Add Inplace CN Doc No.3-4] #7233

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Apr 21, 2025

Conversation

Keywennn
Copy link
Contributor

@Keywennn Keywennn commented Apr 4, 2025

描述:
为bitwise_and_添加中文文档
为bitwise_invert_添加中文文档

增加:
bitwise_and__.rst文件
bitwise_invert__.rst文件

修改:
在Overview_cn.rst中新增bitwise_and__相关信息(在“tensor 数学操作原位(inplace)版本”标题下)
在Overview_cn.rst中新增bitwise_invert__相关信息(在“tensor 数学操作原位(inplace)版本”标题下)

issue:#7090

英文文档链接:https://www.paddlepaddle.org.cn/documentation/docs/en/develop/api/paddle/bitwise_and__en.html

英文文档链接:https://www.paddlepaddle.org.cn/documentation/docs/en/develop/api/paddle/bitwise_invert__en.html

@sunzhongkai588

Copy link

paddle-bot bot commented Apr 4, 2025

感谢你贡献飞桨文档,文档预览构建中,Docs-New 跑完后即可预览,预览链接:http://preview-pr-7233.paddle-docs-preview.paddlepaddle.org.cn/documentation/docs/zh/api/index_cn.html
预览工具的更多说明,请参考:飞桨文档预览工具

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这部分内容和这个PR无关吧

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

是的,这是另一个api

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

是的,这是另一个api

那就删了这部分 @Keywennn

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The conflicts have been resolved. Please review the changes.

Comment on lines 7 to 8
Inplace 版本的 :ref:`cn_api_paddle_bitwise_invert` API,对输入 `x` 采用 Inplace 策略。
更多关于 inplace 操作的介绍请参考 `3.1.3 原位(Inplace)操作和非原位操作的区别`_ 了解详情。
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Inplace 版本的 :ref:`cn_api_paddle_bitwise_invert` API,对输入 `x` 采用 Inplace 策略。
更多关于 inplace 操作的介绍请参考 `3.1.3 原位(Inplace)操作和非原位操作的区别`_ 了解详情。
Inplace 版本的 :ref:`cn_api_paddle_bitwise_invert` API,对输入 `x` 采用 Inplace 策略。
更多关于 inplace 操作的介绍请参考 `3.1.3 原位(Inplace)操作和非原位操作的区别`_ 了解详情。

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已修改

Comment on lines 7 to 8
Inplace 版本的 :ref:`cn_api_paddle_bitwise_and` API,对输入 `x` 采用 Inplace 策略。
更多关于 inplace 操作的介绍请参考 `3.1.3 原位(Inplace)操作和非原位操作的区别`_ 了解详情。
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Inplace 版本的 :ref:`cn_api_paddle_bitwise_and` API,对输入 `x` 采用 Inplace 策略。
更多关于 inplace 操作的介绍请参考 `3.1.3 原位(Inplace)操作和非原位操作的区别`_ 了解详情。
Inplace 版本的 :ref:`cn_api_paddle_bitwise_and` API,对输入 `x` 采用 Inplace 策略。
更多关于 inplace 操作的介绍请参考 `3.1.3 原位(Inplace)操作和非原位操作的区别`_ 了解详情。

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

已修改

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

请查看

@luotao1
Copy link
Collaborator

luotao1 commented Apr 18, 2025

请解决下冲突

Copy link
Collaborator

@sunzhongkai588 sunzhongkai588 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@luotao1 luotao1 merged commit 42093f6 into PaddlePaddle:develop Apr 21, 2025
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
contributor HappyOpenSource 快乐开源活动issue与PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants