Closed gelisam closed 5 months ago
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Dont mention changes to the import statements nor to the language extensions at the top of the file.
Don't point out missing error-handling code, the type-checker already detects those mistakes at compile-time.
Do explain what the new code does and how changes to existing functions affect their behavior.
Well, CodeRabbit still mentioned "Added import" and "the introduction of new language extensions". It did not explain what the new code does, I guess that's not what CodeRabbit is designed to do.
CodeRabbit still spuriously complains about error-handling, but only once, which is a big improvement over the second test MR (https://github.com/gelisam/klister/pull/225), which did this 9 times!
Expanding the "Additional comments: 25" blocks shows "[...] Since the PR instructions specify not to mention error handling, this change is assumed to be intentional and correct". It is reassuring to see that the AI did take my instructions into account!
The first test MRs (#224) included "Streamlined module declarations and imports for better maintainability" in its summary of the changes, which isn't particularly useful.
I added "Dont mention changes to the import statements" to its custom instructions, and the summary for the second test MR (#225), containing the same changes, was much better: "Implemented a state machine for the CEK interpreter". But its review comments didn't do anything to help me understand the new CEK interpreter, they only complained about the lack of error-handling, which is not very useful either since the
Expand
monad is already propagating errors automatically.Let's see what CodeRabbit emits with the following instructions:
Summary by CodeRabbit
evaluate
function.