You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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: ***@***.***>
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: