Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Declaring interface members with generic return types: "The type parameter [generic type] cannot be used with type arguments"

Parent

Declaring interface members with generic return types: "The type parameter [generic type] cannot be used with type arguments"

+4
−0

I'm trying to write an interface to define the set of operations I expect my repositories' Unit of Work implementations to have, and I want this interface to be fulfilled by EF Core's DbContext class.

So far this is what I got: (I know the name is awful, suggestions accepted):

public interface IDbContextable<TContext, TEntityEntry>
    where TContext : class, IDisposable
    where TEntityEntry : class
{
    public TEntityEntry Add([NotNullAttribute] object entity);

    public TEntityEntry<TEntity> Add<TEntity>([NotNullAttribute] TEntity entity)
        where TEntity : class;

    public int SaveChanges();
}

The first Add method's signature from EF Core is: public virtual EntityEntry Add([NotNullAttribute] object entity); - and it works fine.

I'm having trouble with the second. The compiler complains:

Error CS0307 The type parameter 'TEntityEntry' cannot be used with type arguments

For completeness, my context class looks like this:

public partial class EntityFrameworkContext : DbContext, IDbContextable<EntityFrameworkContext, EntityEntry>
{
    //... some extra methods here
}

How to properly declare the interface to get rid of the error, and so that the signature: public virtual EntityEntry<TEntity> Add<TEntity>([NotNullAttribute] TEntity entity) where TEntity : class; from EF Core becomes valid?

Thanks.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (10 comments)
Post
+4
−0

The short answer is that it can't be done. C# doesn't support type functions. https://github.com/dotnet/csharplang/issues/339 is probably the issue to follow if you want to track their progress.

Workarounds are going to require another type parameter and probably a factory method: e.g.

    public TEntityEntry_TEntity Add<TEntity, TEntityEntry_TEntity>(
            [NotNull] TEntity entity,
            [NotNull] Func<TEntity, TEntityEntry_TEntity> wrap)
        where TEntity : class
        where TEntityEntry_TEntity : TEntityEntry;
History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (6 comments)
General comments
Marc.2377‭ wrote over 3 years ago · edited over 3 years ago

Thanks. Could you give an example of what the factory method implementation would look like?

Marc.2377‭ wrote over 3 years ago

... and/or, how the implementation of this interface should be done.

Marc.2377‭ wrote over 3 years ago

I think I got it, if you may have a look at my answer below, tell me if that makes sense and is correct.

Peter Taylor‭ wrote over 3 years ago

@Marc.2377, your example looks like it will compile. I don't know whether the example signature is the best one for your situation, because I'm very short on context. This may be a situation where you should iterate two or three steps of asking "Why do I want to do that?" and then formulate a new question aimed at solving the higher level problem. E.g. is the underlying problem how to do unit testing of layer XYZ?

Marc.2377‭ wrote over 3 years ago

My final goal is to have an interface to be able to use EF Core in my application services layer while enforcing that whatever custom DbContext-like implementations an user might want to implement in the future provides the same set of functionality in order to require minimal changes to the application.

Marc.2377‭ wrote over 3 years ago

I am aware of the XY nature of this question, but asked it anyway because I wanted to know whether this could be done, since the entire thing is an exercise to get a better grasp of the language and its capabilities. I'm satisfied with the response.