The purpose of nt_registry was to access the raw ntdll registry api.  It's not meant to duplicate base (or use it).

If we want to access nt_registry from anywhere other than chrome_elf, I would recommend having a shim/wrapper layer inside of base (that could add scoping usability).  And the static library nt_registry could be a dependency of base.  grt@ was pondering this general idea at some point.

In my opinion, nt_registry should remain raw and as small as possible.  I'm happy to help move this standalone lib under base if we decide that is worth doing!

Sorry, maybe I wasn't clear in the initial report. I'm just using it in chrome_elf, but it still seems a bit cumbersome to require Open/Create to be matched with a corresponding Close, rather than having a ScopedKey helper. Does that seem reasonable? I will prototype what I mean and you can see if you like it.

Oh, did you mean the dependency on base because of using ScopedGeneric? I agree, we wouldn't want to do that. But nt_registry.h could have a simple class with a destructor that does the close.

If just you meant simply that it's "bigger" and less raw with the scoper, I think I disagree. I suspect it'll be less code, and still pretty clear what's happening underneath. But we'd have to try it to be sure, I guess.

Ah ok, feel free to prototype!

https://codereview.chromium.org/2507263002/