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

Extract windows_registry module into its own crate #174

Closed
brson opened this Issue Jul 13, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@brson
Copy link
Contributor

brson commented Jul 13, 2017

This crate is out of place here. Put it in another crate and make an internal dependency of this crate.

I'd suggest calling the crate msvc but we probably need to bikeshed the name further. @retep998 @alexcrichton preferences?

We'll also need to negotiate where it lives. At the least @alexcrichton will need to be a maintainer, so maybe he should just do this one.

@brson brson referenced this issue Jul 13, 2017

Closed

Crate evaluation tracking issue #198

20 of 25 tasks complete
@alexcrichton

This comment has been minimized.

Copy link
Owner

alexcrichton commented Jul 13, 2017

I'd probably go for a name like msvc-finder or something like that, I'm not sure this crate would be good enough to take a good name like msvc!

@retep998

This comment has been minimized.

Copy link
Contributor

retep998 commented Jul 13, 2017

There's also bikeshedding on names in retep998/msvc-bunny#1

@alexcrichton

This comment has been minimized.

Copy link
Owner

alexcrichton commented Sep 19, 2017

I'm going to close this as this isn't going to happen for the 1.0 release. When it does happen, though, I'll happily deprecate the functionality that already exists!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.