So we have an interface like so/// <summary>/// Interface for classes capable of creating foos/// </summary>public interface ICreatesFoo{  /// <summary>  /// Creates foos  /// </summary>  void Create(Foo foo);  /// <summary>  /// Does Bar stuff  /// </summary>  void Bar();}Recently, we played a documentation story which involved generating and ensuring that there is plenty of XML documentation like above. This caused a lot of duplication of documentation though. Example implementation:/// <summary>/// A Foo Creator which is fast/// </summary>public class FastFooCreator : ICreatesFoo{  /// <summary>  /// Creates foos  /// </summary>  public void Create(Foo foo)  {    //insert code here  }  /// <summary>  /// Does Bar stuff  /// </summary>  public void Bar()  {    //code here  }}As you can see the method documentation is a straight rip from the interface. The big question is, is this a bad thing? My gut tells me yes because of duplication, but then again maybe not? Also, we have other similar documentation duplication with override functions and virtual functions.Is this bad and should be avoided, or not? Is it at all worthwhile even?
Duplicating documentation on interface implementations/overrides good or bad?
c#;documentation;xml;documentation generation