Skip to content

fix: use more efficient range over SplitSeq #459

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Aug 1, 2025
Merged

fix: use more efficient range over SplitSeq #459

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion input/chainsync/plugin.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -154,7 +154,7 @@ func NewFromCmdlineOptions() plugin.Plugin {
}
if cmdlineOptions.intersectPoint != "" {
intersectPoints := []ocommon.Point{}
for _, point := range strings.Split(cmdlineOptions.intersectPoint, ",") {
for point := range strings.SplitSeq(cmdlineOptions.intersectPoint, ",") {
intersectPointParts := strings.Split(point, ".")
if len(intersectPointParts) != 2 {
panic("invalid intersect point format")
Expand Down
Loading