Vibe-coding in Crystal

I’ve been using Raptor Mini and Codex to randomly check bug-reproduction code posted in Crystal compiler GitHub issues. They can often point out where the “bug” is.
In the process, I came to understand that the bugs remaining today are more likely to be undecided edge cases in language design than pure bugs. Whether a given snippet passed to the Crystal compiler should work as valid code, or be rejected with an error, depends on human preference. So when creating a pull request, a small statement of what Crystal should be slips in and makes it meaningful.

1 Like

There are other kinds of bugs that might not even reported. For example, improving the API documentation is one of those, IMHO.

1 Like