Conversation
slither is halting CI. It thinks that yul is an antipattern. It is blocking PRs from being merged because of a `if (boolean == false)` check which is completely sane, sure you can do `if (!boolean)` but that is less readable. This commit prevents slither from halting CI. We can figure out how much we want to use slither in the future.
|
✅ Deploy Preview for opstack-docs canceled.
|
|
Slither is passing on develop. Is there a specific PR which is causing it to fail? |
There are a bunch of PRs, see #5356 |
This does look annoying, feels like something a linter should do rather than Slither. The suggestion does look like a valid lint, tho. To break it down:
The optimizer picks this up in the non-IR pipeline most of the time, though. |
trianglesphere
left a comment
There was a problem hiding this comment.
Approving b/c @maurelian approved.
|
This PR has been added to the merge queue, and will be merged soon. |
|
This PR is next in line to be merged, and will be merged as soon as checks pass. |
|
I had a second thought, will update shortly |
|
This was fixed in #5356 by excluding |
Description
slither is halting CI. It thinks that yul is an antipattern. It is blocking PRs from being merged because of a
if (boolean == false)check which is completely sane, sure you can doif (!boolean)but that is less readable. This commit prevents slither from halting CI. We can figure out how much we want to use slither in the future.