> Or add section to explain most common agent comments.
Shouldn't your agent explain its own comments? why would the author of a fast queue care what your agent says?
Shouldn't your agent explain its own comments? why would the author of a fast queue care what your agent says?
Imagine the code compilers (or some analysis tool) gives several concurrency and memory warnings. It has easy workaround (just annotate strange code, with links to explanations that this is workaround for low level bugs).
I am too tired of shitty "safe" Rust code, with 'unsafe' section around every library call (not case here, just an example)! Be clear with that, it takes 15 minutes and 10 cents!
This project could have correct concurrent code and design, but around much narrower definitions. But most people will not go too deep with review to find it!
And if it's got value for you, hey, it's open source. Spend the 15 minutes and 10 cents, it's a bargain.
I don't think this is true at all.
I don't. I review code by hand, like I have for 20 years. I think you might have some sample bias.