dotnet/roslyn

Assert failures handling DynamicObjectCreationExpression in GetValEscape() and CheckValEscape()

Open

#67,518 opened on Mar 28, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (4,257 forks)batch import
Area-CompilersBughelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

Version Used: release/dev17.4: https://github.com/dotnet/roslyn/commit/528676cdbf0bfcfdb9372dc57a047dd0edc6d4db main: https://github.com/dotnet/roslyn/commit/3dee0a96cd8b5478390c47ddb0545875bf6b4c18

Steps to Reproduce:

Compile with DEBUG build:

static class Program
{
    static void Main()
    {
        dynamic d = 0;
        R x = new R(d);
        R y;
        y = new R(default(R), d);
    }
}

readonly ref struct R
{
    public R(int i) { }
    public R(R r, int i) { }
}

Expected Behavior: (8,19): error CS1978: Cannot use an expression of type 'R' as an argument to a dynamically dispatched operation.

Actual Behavior: Assert failures with message "DynamicObjectCreationExpression expression of R type" in GetValEscape() and CheckValEscape().

(8,19): error CS1978: Cannot use an expression of type 'R' as an argument to a dynamically dispatched operation. (8,13): error CS8751: Internal error in the C# compiler.

Contributor guide

Research direction
Inspect the failing test and trace the handler path in GetValEscape() and CheckValEscape() for DynamicObjectCreationExpression.
Tech stack
csharp
Domain
compilers
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC#
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60