Compiler Error CS0525

[teddga]

Type of issue

Other (describe below)

Description

I wrote a stupid Interface, admittedly. My basic idea was to create an IType, IObject and and IEncoding. The intent was to mimic C# class, object and reader/writer. My thoughts were basically to create a simplistic framework of CSharp classes and such.

Here is my problem: "Compiler Error CS0525". It correctly describes the fact that I attempted to create a "field" in my interface.... and claims that this is illegal in CSharp. I don't disagree. I was imagining my own interpretation of how the world works. CSharp has it's own rules and regulations about such thing. I'm happy to agree with CSharp. But.... maybe a hint about how to implement my own needs? I don't care if "string Name" is technically illegal in an interface, but... Exactly why is it Illegal? and exactly why can't I implement a CSharp equivalent ?

The Documentation for CS0525 does not hint at a solution. It does not suggest protentional queries. It just says, "NO YOU CAN'T". But I want to know how to take care of my buisiness. right?

Page URL

https://learn.microsoft.com/en-us/dotnet/csharp/misc/cs0525?f1url=%3FappId%3Droslyn%26k%3Dk(CS0525)

Content source URL

https://github.com/dotnet/docs/blob/main/docs/csharp/misc/cs0525.md

Document Version Independent Id

5cc1abe5-2ab2-7159-f4ca-b2167d8bd719

Platform Id

1f400fa8-d039-c3f2-55db-241f514630ef

Article author

@BillWagner

Metadata

• ID: a0cc20d7-1b1d-ab13-dcba-c1c3f3a530bd
• PlatformId: 1f400fa8-d039-c3f2-55db-241f514630ef
• Service: dotnet-csharp
• Sub-service: errors-warnings

Related Issues

[BillWagner]

Hi @teddga

I can't give a great answer without knowing how your different types relate to each other.

To declare a field that's shared with multiple concrete types, you need to put the field in a base class, possibly an abstract base class.

Because C# also enforces single class inheritance, that may or may not meet your needs.

Another option would be to define a property in the interface that implementors can provide. That's not exactly what you're trying to do, but it has similar semantics at the API level.

Finally, your comment on the error reference content is valid, and it's something that we're slowly addressing across all these articles: They all should link to the conceptual content regarding the language elements used (interface in this case). That's where the background information you're seeking is provided. I'll keep this open in our backlog to address as we work in this area.

[bigboybamo]

Hi @BillWagner , Does this involve just put a link to the general interface doc on the error page? Because it seems like it already exists