-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Embed Resources for backward compatibility #476
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
Conversation
|
Could this cause issues with |
libcontainer/configs/cgroup_unix.go
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I sort of don't understand why we need to embed it? Why just don't use value instead of pointer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, sorry, it's for backward compatibility.
|
Hmm, the idea behind making Resources a pointer was that in the future we can clean up the API so if Resources are nil, we can just join instead of create. |
|
@mrunalp I think we can embed pointer. |
|
Cool. I would prefer that. Sent from my iPhone
|
Fixes: moby/moby#19329 Signed-off-by: Qiang Huang <[email protected]>
2da0993 to
f048eaf
Compare
|
LGTM |
Embed Resources for backward compatibility
|
LGTM |
Fixes: moby/moby#19329
Signed-off-by: Qiang Huang [email protected]