从方法中返回词典(Returning dictionaries from methods)

从方法中返回词典(Returning dictionaries from methods)

这些类型的方法一直困扰着我。 在不深入研究代码的情况下，我不知道该字典中的键或子值应该是什么。 我已经做了大约一千次，我敢肯定。 但它一直困扰着我，因为它缺乏如此多的信息。

IDictionary<int,HashSet<int>> GetExportedCharges() { ... } void GetVisitStatuses(IDictionary<int,HashSet<int>> exportedCharges) { ... }

将材料放在字典中是有意义的，但所有IDictionary方法都有非常抽象的参数。 我想我可以创建一个新类，实现IDictionary，并重命名所有参数。 这看起来有点矫枉过正。 希望c＃有一个'typdef'指令。

你怎么避免像这样回复词典？ 或者你完全避免这种情况？

These types of methods have always bothered me. Without digging through the code, I have no idea what the key or sub-value is supposed to be in this dictionary. I've done this myself about a thousand times, I'm sure. But it has always bothered me because it lacks so much information.

IDictionary<int,HashSet<int>> GetExportedCharges() { ... } void GetVisitStatuses(IDictionary<int,HashSet<int>> exportedCharges) { ... }

Having the material in a dictionary makes sense, but all of the IDictionary methods have very abstract parameters. I suppose I could create a new class, implement IDictionary, and rename all of the parameters. It just seems like overkill. Makes be wish c# had a 'typdef' directive.

How do you avoid returning dictionaries like this? Or do you avoid this at all?

最满意答案

您可能会发现一个非常简单的解决方案：

public class IdToSetOfWidgetNumbersMap : Dictionary<int,HashSet<int>> { }

优点：

看到返回IdToSetOfWidgetNumbersMap的方法并没有留下很多问题 该类可以完全为空，或者如果您愿意，可以选择为Dictionary公开的成员提供别名

坏处：

您需要为每种类型的字典创建一个do-nothing类

There is a very simple solution that you might find adequate:

public class IdToSetOfWidgetNumbersMap : Dictionary<int,HashSet<int>> { }

Advantages:

Seeing a method returning an IdToSetOfWidgetNumbersMap doesn't leave many questions open The class can be left totally empty, or you can choose to provide aliases for the members exposed by Dictionary if you prefer

Disadvantage:

You need to create a do-nothing class for each type of dictionary