-
Notifications
You must be signed in to change notification settings - Fork 222
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
Doc update, mentioning go's native embedding #124
Comments
Up for a PR?
man. 2. mai 2022, 09:00 skrev Amnon ***@***.***>:
… This has been a very useful tool. But the introduction of //go:embed in
Go 1.16 provides roughly the
same functionality, but without requiring a go generate pre-compilation
step.
It would be good to add a comment to the beginning of the readme, saying
that it is best to use go's native embedding,
and to mention any cases which are not handled by go:embed where statik
would still be useful.
—
Reply to this email directly, view it on GitHub
<#124>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXOYATFLVMXVCDQBFPWANDVH54QFANCNFSM5U3EVWVQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This has been a very useful tool. But the introduction of
//go:embed
in Go 1.16 provides roughly thesame functionality, but without requiring a go generate pre-compilation step.
It would be good to add a comment to the beginning of the readme, saying that it is best to use go's native embedding,
and to mention any cases which are not handled by go:embed where statik would still be useful.
The text was updated successfully, but these errors were encountered: