Closed archie2x closed 3 months ago
I'm not entirely convinced we should be doing this. Can you explain why this is needed (and why you can't just use the latest tinygo for example)?
I'm not entirely convinced we should be doing this. Can you explain why this is needed (and why you can't just use the latest tinygo for example)?
Thanks! Sorry: it was an early-morning PR. See Issue #4391 where I tried to illustrate the motivation.
As mentioned in #4391, I agree this doesn't make sense for now.
[ see #4391 for motivation ] This attempts to duplicate big-Go go1.X build tags in tinygo with a series of build tags in the form
tinygo0.1,tinygo0.2,...
Also adds a '-full' command-line flag to see all of the tags.
TODO:
tinygoVersion.Major
etc. instead of goenv.VersionMajor etc.tinygo-dev
build tag if "-dev" ?const Major = 0 const Minor = 33 const Patch = 0 const Dev = "-dev" // "" for release