Skip to content

Conversation

jimidle
Copy link
Collaborator

@jimidle jimidle commented Apr 12, 2023

Keep a few handy files in the internal directory of the go runtime, but exclude the generated things from github.

This makes it trivial to drop in a grammar that users may have found causes go problems, and automatically work on the latest version of the go runtime and tool.

jimidle added 3 commits April 12, 2023 11:56
… be in the repo

Signed-off-by: Jim.Idle <jimi@idle.ws>
@jimidle
Copy link
Collaborator Author

jimidle commented Apr 12, 2023

Seems the Github triggers failed onthe check. No reason not to merge this I think @parrt

jimidle added 2 commits April 13, 2023 11:16
  - I will store this in my own repo and direct any future maintainers to there
    this will avoid any confusion.

Signed-off-by: Jim.Idle <jimi@idle.ws>
Signed-off-by: Jim.Idle <jimi@idle.ws>
@jimidle
Copy link
Collaborator Author

jimidle commented Apr 13, 2023

This should be good to go now fellas. I am going to create a separate repo in my own space to have a test rig for go runtime grammar testing that is separate from the go runtime source.

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

Successfully merging this pull request may close these issues.

3 participants