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

Forbid duplicated namespaces with same type. #597

Merged
merged 1 commit into from
Nov 1, 2016

Conversation

WeiZhang555
Copy link
Contributor

@WeiZhang555 WeiZhang555 commented Oct 27, 2016

Related runc PR: opencontainers/runc#1150

Signed-off-by: Zhang Wei zhangwei555@huawei.com

Signed-off-by: Zhang Wei <zhangwei555@huawei.com>
@wking
Copy link
Contributor

wking commented Oct 27, 2016

Instead of using an array for a structure where order is insignificant
and duplicates are not allowed, I'd rather use an object (since the
just-landed #584, all of our objects forbid duplicates and do not have
significant ordering). I've filed #598 with that approach. I
understand that migrating from an array to an object will be painful,
but I think it's worth it if we have no reason to use arrays for
portable ordering or duplication. One benefit of using an object is
that we get much easier add-or-replace and removal code than hacks
like this 1.

@crosbymichael
Copy link
Member

crosbymichael commented Oct 27, 2016

LGTM

Approved with PullApprove

1 similar comment
@hqhq
Copy link
Contributor

hqhq commented Nov 1, 2016

LGTM

Approved with PullApprove

@hqhq hqhq merged commit b8e2ebe into opencontainers:master Nov 1, 2016
hqhq added a commit to hqhq/runtime-spec that referenced this pull request Nov 3, 2016
Alternative of opencontainers#583 , as what we do for `namespaces`
in opencontainers#597 .

Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
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.

4 participants