Skip to content

IsExternalInit decoding should be more restrictive #44671

New issue
New issue
Closed
#45220
Closed
IsExternalInit decoding should be more restrictive#44671
#45220
Assignees
AlekseyTs
Labels
Area-CompilersFeature - RecordsRecords
@RikkiGibson

Description

@RikkiGibson
RikkiGibson
opened on May 29, 2020

roslyn/src/Compilers/Core/Portable/MetadataReader/MetadataDecoder.cs

Line 1190 in f423b85

// PROTOTYPE(init-only): make this more restrictive (ie. disallow aside from the return value of an instance setter)

roslyn/src/Compilers/CSharp/Test/Semantic/Semantics/InitOnlyMemberTests.cs

Line 3104 in 891fd42

comp.VerifyDiagnostics(); // PROTOTYPE(init-only): expect error diagnostics

roslyn/src/Compilers/CSharp/Test/Semantic/Semantics/InitOnlyMemberTests.cs

Line 2852 in 891fd42

Assert.False(property0.HasUseSiteError); // PROTOTYPE(init-only): expect use-site error

roslyn/src/Compilers/CSharp/Test/Semantic/Semantics/InitOnlyMemberTests.cs

Line 3380 in 891fd42

// PROTOTYPE(init-only): when decoding PE for a ref property, we don't allow IsExternalInit on the return (as opposed to ref return). We don't allow such properties in source.

roslyn/src/Compilers/CSharp/Test/Semantic/Semantics/InitOnlyMemberTests.cs

Line 3465 in 891fd42

// PROTOTYPE(init-only): make this more restrictive (ie. disallow aside from the return value of an instance setter)

Metadata

Metadata

Assignees

Labels

Area-CompilersFeature - RecordsRecords

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions