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

Rename constant NET_NATIVE to netcore50 #16075

Closed
venkat-raman251 opened this issue Jan 11, 2016 · 9 comments
Closed

Rename constant NET_NATIVE to netcore50 #16075

venkat-raman251 opened this issue Jan 11, 2016 · 9 comments
Labels
area-Meta enhancement Product code improvement that does NOT require public API changes/additions help wanted [up-for-grabs] Good issue for external contributors
Milestone

Comments

@venkat-raman251
Copy link
Contributor

This is a tracking issue to rename this constant to follow our naming conventions.

@mellinoe
Copy link
Contributor

I think I've also seen "NETNATIVE" (without the underscore) in some projects as well. Some of them might have snuck into corefx during porting in the past month

@mellinoe
Copy link
Contributor

@weshaggard @venkat-raman251 There are still some instances of NET_NATIVE around the repo. I'm wondering if netcore50 is still the thing that we are using?

@weshaggard
Copy link
Member

We should use the guidance at https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/project-guidelines.md#define-naming-convention and clean-up the remaining projects to make them consistent.

@karelz
Copy link
Member

karelz commented Jan 30, 2017

@weshaggard are you working on it? (it's assigned to you)
Is it still actionable?

@weshaggard weshaggard removed their assignment Jan 30, 2017
@weshaggard
Copy link
Member

I'm not working on this. It is a clean-up item I've not looked through the source recently to see how pervasive it is currently. It is probably worth dividing it into new issues and have the owners of the libraries look into it and decided to violate our guidelines or clean it up.

@karelz
Copy link
Member

karelz commented Jan 30, 2017

I would love to see clear guidance "this is what has to happen". Then, we can justify "up for grabs".
Is it unclear if/what exactly we would do? Do we really need area owners to chime in? If yes, why? (hypothetical example is fine)

@weshaggard
Copy link
Member

When we did a large code dump during the porting exercises there was a lot of code that used the define NET_NATIVE (https://github.com/dotnet/corefx/search?utf8=%E2%9C%93&q=NET_NATIVE) instead of fixing that as part of the code dump we filed this tracking issue to clean these defines up to make them match our guidelines https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/project-guidelines.md#define-naming-convention. So this issue is about updating the defines in those source files to match the guidelines. The defines should match the build configuration.

Looks like most of the projects still using NET_NATIVE are confined to Serialization and XML so we could get those owners to clean-up the source.

@karelz
Copy link
Member

karelz commented Jan 30, 2017

After offline chat with @weshaggard:
It turns out that some NET_NATIVE ifdef'd code will likely be targeting .NET Native (and not CoreCLR in UWP for F5), while some will be general UWP (not .NET Native specific).
Currently we do not have great way to test in UWP (.NET Native or CoreCLR for F5) - that work is in progress.

If/when anyone wants to pick up the work, please ping us - @weshaggard can provide more details and guidance in such case.
The work will likely be a little bit involved (at least on the decision side).

@stephentoub
Copy link
Member

NET_NATIVE no longer shows up anywhere in corefx.

@msftgits msftgits transferred this issue from dotnet/corefx Jan 31, 2020
@msftgits msftgits added this to the 5.0 milestone Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Meta enhancement Product code improvement that does NOT require public API changes/additions help wanted [up-for-grabs] Good issue for external contributors
Projects
None yet
Development

No branches or pull requests

6 participants