Make Maps constructor explicit.

Make Maps constructor explicit.

BUG=https://code.google.com/p/chromium/issues/detail?id=163357
Committed: https://code.google.com/p/seccompsandbox/source/detail?r=189

[hans, 2012-12-12 10:19:58]

Hi Mark, can you take a look at this?

I'm looking into cleaning up missing/superfluous 'explicit' in Chromium.

[Mark Seaborn, 2012-12-12 17:43:12]

LGTM as long as this compiles OK (e.g. run "make test" in this directory).

Are we still using this repo, though?  Markus, is this obsoleted by the
seccomp-bpf sandbox yet?  Should we stop pulling the original seccomp sandbox
into the Chromium repo?

[hans, 2012-12-12 17:45:32]

On 2012/12/12 17:43:12, Mark Seaborn wrote:
> LGTM as long as this compiles OK (e.g. run "make test" in this directory).

Yes, it compiles and the tests pass.

> Are we still using this repo, though?  Markus, is this obsoleted by the
> seccomp-bpf sandbox yet?  Should we stop pulling the original seccomp sandbox
> into the Chromium repo?

At least it seems to get compiled as part of the Chromium build on my Linux box.

[Markus (顧孟勤), 2012-12-12 17:57:02]

It is somewhat obsolete, but we still keep it around for reference. We'll
probably revisit that decision in the new year, as the new sandbox has been
maturing nicely.


Markus

On Wednesday, December 12, 2012,  <mseaborn@chromium.org> wrote:
> LGTM as long as this compiles OK (e.g. run "make test" in this directory).
>
> Are we still using this repo, though?  Markus, is this obsoleted by the
> seccomp-bpf sandbox yet?  Should we stop pulling the original seccomp
sandbox
> into the Chromium repo?
>
> https://codereview.chromium.org/11547014/
>