Skip to main content

Return to Question

replaced http://stackoverflow.com/ with https://stackoverflow.com/

edited May 23, 2017 at 12:40

edited May 23, 2017 at 12:40

1

Is C# 4.0 Tuple covariant Is C# 4.0 Tuple covariant
Co/Contravariance? Tuple<string, IEnumerable> not satisfied with List Co/Contravariance? Tuple<string, IEnumerable> not satisfied with List

deleted 19 characters in body

edited Jul 19, 2015 at 1:29

edited Jul 19, 2015 at 1:29

35.2k
13
134
238

So I decide to make my own implementation of an interface which subclass a tuple with a support for Covariance:

First problem : subclass and equality support Problems:

Subclass and equality support

Second problem : naming convention

Naming convention

So I decide to make my own implementation of an interface which subclass a tuple with a support for Covariance:

First problem : subclass and equality support

Second problem : naming convention

I decide to make my own implementation of an interface which subclass a tuple with a support for Covariance:

Problems:

Subclass and equality support

Naming convention

Tweeted twitter.com/#!/StackCodeReview/status/402512016541491200

occurred Nov 18, 2013 at 19:01

occurred Nov 18, 2013 at 19:01

added 481 characters in body

edited Nov 18, 2013 at 15:33

edited Nov 18, 2013 at 15:33

243
1
9

First problem : subclass and equality support

Subclassing the tuple is easy and there is nothing to do, and this is my concern. Is there something am I missing? I see no reason why equalities and hashcode souldn't work as expected with classic Tuple, but maybe you will find a problem somewhere which I didn't think of.

Second problem : naming convention

Like the static class Tuple contains all the Create static methods, ITuple, which is not an interface, has the static builder. At what point is this weird to name a non interface with an I prefix?
At first, I called the ITuple interface ICovariantTuple, but found it too long, and there is no ITuple in the framework. Is this evident that ITuple is covariant?

Subclassing the tuple is easy and there is nothing to do, and this is my concern. Is there something am I missing? I see no reason why equalities and hashcode souldn't work as expected with classic Tuple, but maybe you will find a problem somewhere which I didn't think of.

First problem : subclass and equality support

Subclassing the tuple is easy and there is nothing to do, and this is my concern. Is there something am I missing? I see no reason why equalities and hashcode souldn't work as expected with classic Tuple, but maybe you will find a problem somewhere which I didn't think of.

Second problem : naming convention

Like the static class Tuple contains all the Create static methods, ITuple, which is not an interface, has the static builder. At what point is this weird to name a non interface with an I prefix?
At first, I called the ITuple interface ICovariantTuple, but found it too long, and there is no ITuple in the framework. Is this evident that ITuple is covariant?

asked Nov 18, 2013 at 15:01

asked Nov 18, 2013 at 15:01

243
1
9

Loading

lang-cs