We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now, we garble the source code within filenames in each package, but not the filenames themselves.
We could join all the source into a single all.go file, so that one can't get any context or meaning from the original file structure or naming.
all.go
The text was updated successfully, but these errors were encountered:
I just realised that joining all source files is not a good option, because then we'd have to worry about file-scoped syntax like build tags.
Sorry, something went wrong.
302cc13
No branches or pull requests
Right now, we garble the source code within filenames in each package, but not the filenames themselves.
We could join all the source into a single
all.go
file, so that one can't get any context or meaning from the original file structure or naming.The text was updated successfully, but these errors were encountered: