Follow zu2 renaming its vertices to nodes - #107
Open
tamnd wants to merge 1 commit into
Open
Conversation
The zu2 C API calls them nodes now, which is the word the rest of the program uses, so the adapter follows: zu2_add_node, zu2_node_of, zu2_nodes and max_nodes. No behaviour changes and the prose in here moves with the calls.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The zu2 C API calls them nodes now, which is the word the rest of the program uses, so the in process adapter follows: zu2_add_node, zu2_node_of, zu2_nodes and max_nodes, and the prose in the file moves with the calls.
Nothing else changes. No behaviour, no flags, no results.
Needs tamnd/zu#411, which is where the rename happens. Building the zu2 adapter against an older libzu2 fails at the link, which is the intended way round: the header and the adapter are one thing.
Built here with
go build -tags zu2inproc ./...against a localcargo build --release -p zu2-capi.