Is Using .NET 4.0 Tuples in my C# Code a Poor Design Decision?

Tuples are great if you control both creating and using them – you can maintain context, which is essential to understanding them.

On a public API, however, they are less effective. The consumer (not you) has to either guess or look up documentation, especially for things like Tuple<int, int>.

I would use them for private/internal members, but use result classes for public/protected members.

This answer also has some info.

Leave a Comment