Consider naming for ILLink.Shared project

[tlakollo]

The shared project allows to share common code in a seamless way for Analyzer and linker in the dotnet/linker project, but is also code that is common in the NativeAOT repo. Although NativeAOT has to have a copy on its own for the shared project they can take advantage of the code inside the project. PR dotnet/runtime#63230 adds the ILLink.Shared project to NativeAOT to have common diagnostics with Linker and Analyzer. One of the concerns is the name of this project, for dotnet/linker is accurate but it can confuse users of the NativeAOT area

The new name should cover the uses of the project which currently is diagnostics, but eventually will contain other shared code

cc @vitek-karas @sbomer @agocke @MichalStrehovsky

[vitek-karas]

This should include changing the namespace of all the types in the shared project. The current ILLink.Shared is weird for two reasons:

• ILLink as an identifier is not used anywhere in the linker itself, the namespaces there are Mono.Linker....
• The code is not specific to illink as a tool as mentioned above as it's going to be used by NativeAOT

I don't think it should use the "public API" naming either - nothing like Microsoft.* or similar as I don't see us exporting these types as API to anything.

So maybe something like Trimming (both as a project name and as the root namespace)?

[MichalStrehovsky]

The single file analyzer also uses this so I would try to go for something more general. Something along the lines of FormFactorAnalysis (based on the form factors doc) might work, but also that name means nothing to someone who didn't read the doc, so maybe not...

[vitek-karas]

We had an offline discussion on this topic, without a clear outcome, but there were some interesting observations:

• Since we don't know exactly what will this be for (yet), we could name it by "organization", basically no semantic meaning, just the name where it came from. Similar idea would be to use a new name without any meaning.
• This code is never expected to become a public API, so the name is not that important and can be changed with relative ease.
• Several people prefer naming based on the purpose of the code and ignore organization/origin as much as possible.

I'll let everybody chime in with their favorite names:
/cc @agocke @sbomer @tlakollo @jtschuster

[vitek-karas]

I personally prefer "descriptive name" over anything else. In this regard I like the NativeAOT namespace ILCompiler - that's what it is.

So following that logic I think these names (both for project and namespace root) would work well:

• ILAnalysis
• ILStaticAnalysis

They're a bit ambitious (probably too general), but they fit what the code is about well and they don't infer any org/tool origin.