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

Refactor rollup #4184

Merged
merged 2 commits into from
Oct 23, 2019
Merged

Refactor rollup #4184

merged 2 commits into from
Oct 23, 2019

Conversation

animesh2049
Copy link
Contributor

@animesh2049 animesh2049 commented Oct 17, 2019

Non multi-part list check doesn't need to happen again and again.


This change is Reviewable

Copy link

@pullrequest pullrequest bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ A review job has been created and sent to the PullRequest network.


@animesh2049 you can click here to see the review status or cancel the code review job.

Copy link

@pullrequest pullrequest bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left an inline question regarding multiple init calls.


Reviewed with ❤️ by PullRequest

posting/list.go Outdated
plist = out.plist
endUid = math.MaxUint64
} else {
init()
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the execution flow and had a question. When init is called on line 835, is it possible to also be called on line 843?

Copy link
Contributor Author

@animesh2049 animesh2049 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 1 files reviewed, 1 unresolved discussion (waiting on @manishrjain, @martinmr, and @pullrequest[bot])


posting/list.go, line 834 at r1 (raw file):

Previously, pullrequest[bot] wrote…

Reviewed the execution flow and had a question. When init is called on line 835, is it possible to also be called on line 843?

l.plist.Splits isn't changing, so this check isn't really needed there.

Copy link
Contributor

@manishrjain manishrjain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks alright from my end. Defer to @martinmr for final approval.

Reviewable status: 0 of 1 files reviewed, 2 unresolved discussions (waiting on @animesh2049, @manishrjain, @martinmr, and @pullrequest[bot])


posting/list.go, line 814 at r1 (raw file):

	// Method to properly initialize all the variables described above.
	init := func() {

update

Copy link
Contributor

@martinmr martinmr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Just address the comment on the function name.

Reviewed 1 of 1 files at r1.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @manishrjain and @pullrequest[bot])


posting/list.go, line 814 at r1 (raw file):

Previously, manishrjain (Manish R Jain) wrote…

update

rename to something like initializeSplit.

The purpose of this method is to move us to the next list in a multi-part list when the iteration detects that a list boundary has been crossed.

Also update the documentation for this method to

// Method to properly initialize the variables above when a multi-part list boundary is crossed.

since the current one is pretty generic.

Copy link
Contributor Author

@animesh2049 animesh2049 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: 0 of 1 files reviewed, 2 unresolved discussions (waiting on @manishrjain, @martinmr, and @pullrequest[bot])


posting/list.go, line 814 at r1 (raw file):

Previously, martinmr (Martin Martinez Rivera) wrote…

rename to something like initializeSplit.

The purpose of this method is to move us to the next list in a multi-part list when the iteration detects that a list boundary has been crossed.

Also update the documentation for this method to

// Method to properly initialize the variables above when a multi-part list boundary is crossed.

since the current one is pretty generic.

Done.

Copy link
Contributor

@martinmr martinmr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewed 1 of 1 files at r2.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @manishrjain and @pullrequest[bot])

@animesh2049 animesh2049 merged commit 31de87c into master Oct 23, 2019
@animesh2049 animesh2049 deleted the animesh2049/minor_refactor branch October 23, 2019 09:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants