[generator] Place interface alternatives [Register] classes in dummy package. #1242
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #802
For interfaces that contain
staticconstsor other members that traditionally could not be placed in a C#interfacewe create anabstract classwith aninternalconstructor that contains the members so users could access them. However, we place a[Register]on them that points to the originalinterface. This can cause problems when trying to resolve Java -> C# types, as multiple C# types[Register]the same Java type:We tried to remove these
[Register]attributes by default, but then JCWs would get generated for them as they inherit JLO and no longer hadDoNotGenerateAcw. Instead, we will place them in a dummy package (mono/internal/etc) so that any user that finds them will get a hint that they are "internal" details. (Note that we will never actually generate the JCW files because ofDoNotGenerateAcw.)dotnet/androidtest PR: dotnet/android#9196