I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

Interesting. Most seem to be testing types in the DLR / CSharp dynamic binder code which effectively we own. Looks like a handful of other types hit this but it is more common than I would've expected.

Can we just fix the casing? I assume they're all internal and we wouldn't write new code this way. Unless you want to dog food your warning.

Can we just fix the casing?

That's an option too, but is a bit more work. So you tell me what you'd like ;-)
How about upper-casing the ones in the product code, but leaving the tests merely escaped?

I'd prefer to upper case them all, but if that's a hassle this change is OK to me.

Thanks for letting me know. I'll take a stab.

How should rtmsg, nlmsgerr and nlmsghdr be capitalized?

Tagging subscribers to this area: @dotnet/area-meta
See info in area-owners.md if you want to be subscribed.

How should rtmsg, nlmsgerr and nlmsghdr be capitalized?

I'd prefer to leave these lower-cased. We have a policy that types/functions declared in C# for interop should mirror the native naming, as if we were able to simply reference a .h file. On Unix, that invariably means lower-cased names.

Then hostent, cgroups, procfs should be left lower-cased too?

Then hostent, cgroups, procfs should be left lower-cased too?

Similarly my preference is for those to remain lower-cased as well.

merged with libraries builds failing, affecting everyone else