Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check in simple end-to-end test for covariant returns. #46285

Merged

Conversation

gafter
Copy link
Member

@gafter gafter commented Jul 23, 2020

No description provided.

@gafter gafter added Area-Compilers Feature - Covariant Returns Permit an override to return a more specific reference type labels Jul 23, 2020
@gafter gafter added this to the 16.8 milestone Jul 23, 2020
@gafter gafter self-assigned this Jul 23, 2020
@gafter
Copy link
Member Author

gafter commented Jul 24, 2020

/cc @jaredpar

jaredpar and others added 3 commits July 24, 2020 09:04
Add a canary test that fails on a runtime supporting covaraint returns to make sure we're testing CI
@gafter gafter marked this pull request as ready for review July 24, 2020 20:05
@gafter gafter requested review from a team as code owners July 24, 2020 20:05
@gafter gafter requested a review from jaredpar July 24, 2020 20:05
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approval

jcouv
jcouv previously approved these changes Jul 24, 2020
Copy link
Member

@jcouv jcouv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM Thanks (iteration 5)

@jcouv jcouv dismissed their stale review July 24, 2020 22:55

Sorry, approved wrong PR

@@ -4,7 +4,7 @@
<PropertyGroup>
<OutputType>Library</OutputType>
<RootNamespace>Microsoft.CodeAnalysis.CSharp.UnitTests</RootNamespace>
<TargetFrameworks>netcoreapp3.1;net472</TargetFrameworks>
<TargetFrameworks>net5.0;net472</TargetFrameworks>
Copy link
Member

@jcouv jcouv Jul 24, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to confirm, we're intentionally keeping our other test projects targeting netcoreapp3.1? #Resolved

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect it is @jaredpar's intention to switch them all at some point.


In reply to: 460321746 [](ancestors = 460321746)


static CovariantReturnTests()
{
if (new CovarantReturnRuntimeOnly().ShouldSkip)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CovarantReturnRuntimeOnly [](start = 20, length = 25)

typo: Covariant

@jcouv jcouv self-assigned this Jul 24, 2020
Neal Gafter and others added 4 commits July 27, 2020 08:49
This updates our build to support the use of `net5.0` as a target
framework inside of our repository.

Note: this is back porting some changes from the covariant returns
branch. Wanted to get them into master sooner so we get more exposure to
them.
@gafter gafter merged commit f9959b5 into dotnet:features/covariant-returns Jul 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Compilers auto-merge Feature - Covariant Returns Permit an override to return a more specific reference type
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants