Skip to content
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

Dev 29/upgrade go 1.23 #30

Merged
merged 11 commits into from
Oct 1, 2024
Merged

Dev 29/upgrade go 1.23 #30

merged 11 commits into from
Oct 1, 2024

Conversation

vibridi
Copy link
Collaborator

@vibridi vibridi commented Sep 30, 2024

No description provided.

Isolated nodes are processed as separate connected components and connected components with one node are short-circuited as of commit ccd6690
This change reflects the actual usage of this struct field, i.e. the layers are iterated as an ordered sequence, mostly top-to-bottom. As a matter of fact, this allows to rewrite several for-loops in the form i:=0;i<len(g.Layers);i++ as simple ranges: the index form was used to enforce a deterministic order when iterating over map entries. Indexing the slice with g.Layers[node.Layer] doesn't change the program semantics from when it was a map, as the Layers slice is initialized in postprocessing of phase 2 based on the node.Layer indices.
@vibridi vibridi merged commit 30f1943 into main Oct 1, 2024
1 check passed
@vibridi vibridi linked an issue Oct 1, 2024 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade to Go 1.23
1 participant