Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add advice about using AI for code generation #765

Merged
merged 1 commit into from
Oct 7, 2024

Conversation

patricoferris
Copy link
Collaborator

cc: @talex5 and @avsm

This is based on #763. Happy for it to say something different, but thought I would get the ball rolling here.

Copy link
Collaborator

@talex5 talex5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks - that looks useful!

For licensing, a lot of what Eio is doing is similar to what the OCaml stdlib does. The stdlib has a different license, and the compiler devs have explicitly told us we can't use their code (e.g. #352 (comment)). I suspect that when asking AI to write e.g. Windows C stubs it will just copy this one source.

Using AI as a search feature to find approaches you didn't know about might be useful though. Though in my limited testing, I found it sends you down the wrong path too often to be useful.

@patricoferris patricoferris merged commit 216ccff into main Oct 7, 2024
8 checks passed
@patricoferris patricoferris deleted the ai-hacking-guidance branch October 7, 2024 12:22
@avsm
Copy link
Contributor

avsm commented Oct 7, 2024

LGTM also; we can revise this in the future but good to be conservative now from a licensing perspective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants