quantpoet

Results 5 issues of quantpoet

The new version of Go has been optimized, and variables do not need to be reassigned. For more info: https://tip.golang.org/wiki/LoopvarExperiment#does-this-mean-i-dont-have-to-write-x--x-in-my-loops-anymore

**What changed?** The new version of Go has been optimized, and variables do not need to be reassigned. **Why?** **How did you test it?** **Potential risks** **Release notes** **Documentation Changes**

**What changed?** The version of revive is too low and needs to be upgraded For https://github.com/cadence-workflow/cadence/pull/7260 **Why?** **How did you test it?** **Potential risks** **Release notes** **Documentation Changes**

Fixed some potential use-after-free bugs identified by static analysis in the core-text crate. The issues were caused by improper lifetime management of Core Foundation objects where raw pointers were being...

Replaced the load-then-store pattern in the fetch() function with compare_exchange to eliminate the race condition where multiple threads could simultaneously cache the same symbol lookup result, preventing potential data corruption...