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
Due to the introduction of incompatible changes to loop in Go 1.22, this may cause potential bugs in our program. Therefore, we've created this issue to track related matters.
We can reduce the likelihood of bugs from the following perspectives:
1. Fullsync
2. For our own code, review the codes that cause inconsistent compiler behavior.
The following indicates the specific ourself's codes where may lead to changes in compiler behavior (generated and organized based on official tools(list at bottom)).
# github.com/iotexproject/iotex-core/v2/action/protocol/execution/evm
action/protocol/execution/evm/evmstatedbadapter.go:730:9: loop variable addr now per-iteration, stack-allocated
action/protocol/execution/evm/evmstatedbadapter.go:1067:9: loop variable addr now per-iteration, heap-allocated
action/protocol/execution/evm/evmstatedbadapter.go:1090:9: loop variable addr now per-iteration, heap-allocated
action/protocol/execution/evm/evmstatedbadapter.go:1098:6: loop variable addr now per-iteration, stack-allocated
# github.com/iotexproject/iotex-core/v2/blockchain/blockdao
blockchain/blockdao/blockdao.go:146:6: loop variable i now per-iteration, stack-allocated
# github.com/iotexproject/iotex-core/v2/blockindex
blockindex/bloomfilterindexer.go:333:11: loop variable topic now per-iteration, stack-allocated
blockindex/bloomfilterindexer.go:349:11: loop variable topic now per-iteration, stack-allocated
# github.com/iotexproject/iotex-election/committee
../go/pkg/mod/github.com/iotexproject/[email protected]/committee/recordtableoperator.go:199:7: loop variable h now per-iteration, stack-allocated
../go/pkg/mod/github.com/iotexproject/[email protected]/committee/deltarecordtableoperator.go:192:7: loop variable h now per-iteration, stack-allocated
# github.com/iotexproject/iotex-core/v2/action/protocol/poll
action/protocol/poll/lifelong_protocol.go:33:9: loop variable delegate now per-iteration, stack-allocated
# github.com/iotexproject/iotex-core/v2/state/factory
state/factory/workingset.go:442:15: loop variable receivedNonces now per-iteration, stack-allocated
state/factory/util.go:69:11: loop variable topic now per-iteration, heap-allocated
# github.com/iotexproject/iotex-core/v2/api
api/grpcserver.go:700:9: loop variable log now per-iteration, stack-allocated
api/grpcserver.go:702:10: loop variable s now per-iteration, stack-allocated
api/web3server_marshal.go:418:9: loop variable tpc now per-iteration, stack-allocated
api/web3server_utils.go:597:13: loop variable log now per-iteration, stack-allocated
3. For third-party dependencies, upgrade to the new version if it already supports Go 1.22 whenever possible.
The following lists third-party dependency libraries that may lead to changes in compiler behavior.
Due to the introduction of incompatible changes to loop in Go 1.22, this may cause potential bugs in our program. Therefore, we've created this issue to track related matters.
We can reduce the likelihood of bugs from the following perspectives:
1. Fullsync
2. For our own code, review the codes that cause inconsistent compiler behavior.
The following indicates the specific ourself's codes where may lead to changes in compiler behavior (generated and organized based on official tools(list at bottom)).
3. For third-party dependencies, upgrade to the new version if it already supports Go 1.22 whenever possible.
The following lists third-party dependency libraries that may lead to changes in compiler behavior.
see-places-of-code-affected
the full loop.log
The text was updated successfully, but these errors were encountered: