[API Proposal]: Obsolete attributes under S.R.CompilerServices with no effect

[huoyaoyuan]

Background and motivation

In #40622 and #43247, SuppressIldasmAttribute and DisablePrivateReflectionAttribute were obsoleted because the runtime and toolchain no longer respects them. There are other attributes no longer respected by coreclr for a long time. PRs like #112975 are also removing the runtime definition of them. We may like to obsolete these attributes to provide a clear indication.

The list of attributes are:

• DefaultDependencyAttribute
• DependencyAttribute
• CompilationRelaxationsAttribute still emitted by roslyn
• CompilerGlobalScopeAttribute still used by VS debugger
• StringFreezingAttribute
• LoaderOptimizationAttribute

API Proposal

namespace System.Runtime.CompilerServices;
{
+   [Obsolete("LoadHint has no effect on .NET 5+", Id = ???1)]
    public partial class DefaultDependencyAttribute {}

+   [Obsolete("LoadHint has no effect on .NET 5+", Id = ???1)]
    public partial class DependencyAttribute {}

+   [Obsolete("LoadHint has no effect on .NET 5+", Id = ???1)]
    public enum LoadHint {}

+   [Obsolete("StringFreezingAttribute has no effect on .NET 5+", Id = ???2)]
    public partial class StringFreezingAttribute{}
}

namespace System
{
+   [Obsolete("LoaderOptimizationAttribute has no effect on .NET 5+", Id = ???3)]
    public partial class LoaderOptimizationAttribute {}
+   [Obsolete("LoaderOptimizationAttribute has no effect on .NET 5+", Id = ???3)]
    public enum LoaderOptimization {}
}

API Usage

N/A

Alternative Designs

How should the IDs and messages be grouped? Grouping related attributes and enum with a same ID seems reasonable.

Should the message say ".NET 5+" or ".NET 10+"? These attributes have not been respected for a long time.

Risks

We shouldn't want to re-introduce these capabilities in the future.

[dotnet-policy-service]

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

[teo-tsirpanis]

Roslyn emits [assembly:CompilationRelaxationsAttribute(CompilationRelaxations.NoStringInterning)] in all assemblies it compiles. If we want to obsolete this attribute I think we should also update Roslyn to not emit it (maybe by checking if it is obsolete?).

[KalleOlaviNiemitalo]

The documentation of CompilerGlobalScopeAttribute says:

This class is used only for communication with debugger tools.

Do debuggers ignore this attribute nowadays?

[huoyaoyuan]

The documentation of CompilerGlobalScopeAttribute says:

This class is used only for communication with debugger tools.

The code comment says "VS 7 debugger":

runtime/src/libraries/System.Private.CoreLib/src/System/Runtime/CompilerServices/CompilerGlobalScopeAttribute.cs

Line 6 in b658cd2

// Attribute used to communicate to the VS7 debugger that a class should be treated as if it has global scope.

I searched runtime and diagnostics and didn't find usage in production code. However, there is some unit test mentioning it:

runtime/src/tests/Loader/classloader/regressions/dev11_11333/dev11_11333.il

Line 30 in b658cd2

.custom instance void [mscorlib]System.Runtime.CompilerServices.CompilerGlobalScopeAttribute::.ctor() = ( 01 00 00 00 )

[huoyaoyuan]

Code handling CompilationRelaxations.NoStringInterning was deleted in #57693 and #64521. There's still a piece of comment mentioning it at

runtime/src/coreclr/vm/jitinterface.cpp

Line 13477 in b658cd2

// We need to update strings atomically (due to NoStringInterning attribute). Note

[jkotas]

PRs like #112975 are also removing the runtime definition of them

Nit: This PR is deleting unused flags on obsolete hosting API. Some of these flags served similar purpose as some of the attributes, but this PR is not deleting runtime definition of any attributes.

Did you mean to include LoaderOptimizationAttribute that was discussed in that PR in this list?

BTW: There is a lot of attributes in the security namespaces that are candidates for obsoletion as well. For example, SecurityTransparentAttribute, SecuritySafeCriticalAttribute, SecurityRulesAttribute, SuppressUnmanagedCodeSecurityAttribute, ... .

CompilerGlobalScopeAttribute
This class is used only for communication with debugger tools.
I searched runtime and diagnostics and didn't find usage in production code.

You would have to search the closed source Visual Studio code that's the production debugger code. The attribute is used there as you can tell by looking at the binaries:

C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\VC\vcpackages>findstr /M CompilerGlobalScopeAttribute vcpkg.dll
vcpkg.dll

The code comment says "VS 7 debugger":

You can delete the version number from the comment so that people are confused by it.

CompilationRelaxations.NoStringInterning

Yes, it was deleted in the runtime. However, the Roslyn still emits it and there may be tools out there that may depend on this attribute. We would have to overall plan for these other places to really obsolete it. I do not think it is worth it to bother with obsoleting this one.

[huoyaoyuan]

Updated original post. I didn't find other attributes in System namespace that looks obsolete.

BTW: There is a lot of attributes in the security namespaces that are candidates for obsoletion as well.

Should they be included in one issue? Many of them already have members obsoleted.

[jkotas]

Should they be included in one issue?

They can be listed in this issue or in a new issue. It does not matter a whole lot.

Should the message say ".NET 5+" or ".NET 10+"?

Vast majority of the obsoletion messages does not mention any version numbers: https://github.com/dotnet/runtime/blob/main/docs/project/list-of-diagnostics.md#obsoletion-diagnostics-syslib0001---syslib0999 . (A few messages do mention a version number. I guess it was an oversight.)

[dotnet-policy-service]

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.