Closed ChrisCatCP closed 4 months ago
Bot detected the issue body's language is not English, translate it automatically.
It has been modified
去掉空行了 顺便问下 项目不准备加.clang-format吗
Bot detected the issue body's language is not English, translate it automatically.
The blank lines have been removed. By the way, are you not going to add .clang-format to the project?
还是没懂,为啥要额外加三,不能直接挪外面定义。。另外 什么情况下 infd 会等于 outfd?
Bot detected the issue body's language is not English, translate it automatically.
I still don’t understand why we need to add an extra three. We can’t just move the definition outside. . In addition, under what circumstances will infd equal outfd?
去掉空行了 顺便问下 项目不准备加.clang-format吗
如果你能整出一个完全符合当前风格的 format ,那可以加,前提是要完全风格一致。
Bot detected the issue body's language is not English, translate it automatically.
Removed the blank lines. By the way, are you not going to add .clang-format to the project?
If you can create a format that completely matches the current style, you can add it, provided that the style is completely consistent.
感觉还得你自己加才行
Bot detected the issue body's language is not English, translate it automatically.
I feel like you have to add it yourself.
还是没懂,为啥要额外加三,不能直接挪外面定义。。另外 什么情况下 infd 会等于 outfd?
额外加三个是因为不想改497 行那边的变量名 不然还是得加三个变量名 差不多的 in和out err 一般情况下确实不会相同吧 但是感觉还是判断下好
Bot detected the issue body's language is not English, translate it automatically.
I still don’t understand why we need to add an extra three. We can’t just move the definition outside. . In addition, under what circumstances will infd equal outfd?
The reason I added three extra variables is because I don’t want to change the variable name on line 497. Otherwise, I still have to add three variable names. It’s almost the same. In and out err are indeed not the same under normal circumstances, but it feels like it is better to make a judgment.
额外加三个是因为不想改497 行那边的变量名 不然还是得加三个变量名 差不多的
为啥要改名,同样用 infd ,又不可能同时存在 file 和 pipe 的 infd,而且都是要 close 的。。而且 openfile 的 三个 fd ,也不可能重复,即使重复,走的 close 逻辑也是跟 pipe 一样的。。完全可以一起在外面定义。
in和out err 一般情况下确实不会相同吧 但是感觉还是判断下好
既然不可能相同,干嘛还要去做冗余的无意义判断。。而且目前的 if 判断太复杂了,能尽可能精简尽量精简
Bot detected the issue body's language is not English, translate it automatically.
I added three extra ones because I don’t want to change the variable name on line 497, otherwise I still have to add three variable names. It’s almost the same.
Why do we need to change the name? We also use infd, and it is impossible to have infd for file and pipe at the same time, and they both need to be closed. . Moreover, the three fds of openfile cannot be repeated. Even if they are repeated, the close logic is the same as that of pipe. . It can be defined outside together.
In and out err are generally not the same, but it feels better to make a judgment.
Since it can't be the same, why bother making redundant and meaningless judgments. . Moreover, the current if judgment is too complicated. It can be simplified as much as possible.
感觉还得你自己加才行
我就是因为懒得加,所以没加。。没这么多时间折腾这个,反正自己敲代码都是手动 format 的,自己完全没这个需求,除非有现成 pr 过来。
Bot detected the issue body's language is not English, translate it automatically.
I feel like you have to add it yourself
I just didn't add it because I was too lazy to add it. . I don’t have so much time to bother with this. Anyway, I type the code manually and format it. I have no need for this at all, unless there is a ready-made PR.
修改了 看了下可能 确实in和out err不可能相等 已经都改过来了
Bot detected the issue body's language is not English, translate it automatically.
Modified. After looking at the possibility, it is true that in and out err cannot be equal. They have been changed.
merge 了
Bot detected the issue body's language is not English, translate it automatically.
Merged
好的 好的
Bot detected the issue body's language is not English, translate it automatically.
ok ok
已经修改了