fix: move build tags to file beginning before copyright header #95
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
//go:build
syntax alongside legacy// +build
syntax for compatibilityProblem
Build tags were placed after copyright headers, causing them to be ignored by the Go compiler. This resulted in Windows cross-compilation errors where both
os_posix.go
andos_windows.go
were compiled together, leading to duplicate declarations:Solution
According to Go's build tag specification, build constraints must be placed at the beginning of the file before any other comments. This fix moves the build tags to the proper location.