Home/ Questions/Q 48373
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T16:16:11+00:00

In other words, is it correct to use: public class CustomerList : System.Collections.Generic.List<Customer> {

  • 0

In other words, is it correct to use:

public class CustomerList : System.Collections.Generic.List<Customer> {     /// supposed to be empty }

instead of:

using CustomerList = System.Collections.Generic.List<Customer>

I’d rather use the first approach because I’d just define CustomerList once, and every time I needed a customer list I’d always use the same type. On the other hand, using the name aliasing approach not only forces me to have to redefine it everywhere, but also a different alias could be given every time someone wanted to use it (think of a big team), and thus cause the code to be less readable.

Please note that the intention in this case would never be to extend the class, just to create an alias.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Don’t do it. When people read:

    List<Customer>

    they immediately understand it. When they read: 

    CustomerList

    they have to go and figure out what a CustomerList is, and that makes your code harder to read. Unless you are the only one working on your codebase, writing readable code is a good idea.

    • 0