Skip to content

Conversation

@nojaf
Copy link
Contributor

@nojaf nojaf commented Aug 23, 2022

I believe this fixes #13761.

@nojaf nojaf force-pushed the signature-types-in-shared-namespace branch from 6ed32ff to 4dc12be Compare August 23, 2022 17:05
@nojaf nojaf force-pushed the signature-types-in-shared-namespace branch from 4dc12be to 51478b6 Compare August 23, 2022 17:20
@nojaf nojaf marked this pull request as ready for review August 23, 2022 17:20
@dsyme
Copy link
Contributor

dsyme commented Aug 23, 2022

The fix seems strange. It feels like a reimplementation of isConcreteNamespace. But I need to look more carefully, just looking on my phone right now.

@nojaf
Copy link
Contributor Author

nojaf commented Aug 24, 2022

Yes, I believe I can re-use isConcreteNamespace to get the same result.

@dsyme dsyme merged commit 710a5d1 into dotnet:main Aug 24, 2022
@nojaf nojaf deleted the signature-types-in-shared-namespace branch August 24, 2022 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Signature file generation does not handle types from a shared namespace

2 participants