-
Notifications
You must be signed in to change notification settings - Fork 0
simplify the FunctionalOptions by removing the Options struct #20
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
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
machines/extism/compiler/options.go:114
- Directly comparing an atomic.Value with its zero value may be unreliable. Consider using a dedicated flag or checking if c.entryPointName.Load() returns nil for proper initialization.
if c.entryPointName == (atomic.Value{}) {
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
machines/extism/compiler/compiler.go:137
- The removal of atomic.Value for entryPointName means that if this field may be updated concurrently after initialization, it could lead to data races. Consider using a concurrency-safe mechanism (such as sync/atomic or mutex protection) if concurrent modifications are expected.
func (c *Compiler) SetEntryPointName(fName string) { c.entryPointName = fName }
|
No description provided.