Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

C# Intermediate C# Polymorphism Review

Chris Braun
Chris Braun
1,606 Points
Posted by Chris Braun
Chris Braun
1,606 Points

Level construction parameters

Is there a reason why the constructor of Level doesn't take both an array of invaders and an array of towers as parameters? Wouldn't this be clearer/simpler? Is it just to demonstrate how the Towers property of the Level object can be initialized at the same time as the construction of the Level object, or is there a deeper rationale behind it? Thanks.

Adam Fields
.a{fill-rule:evenodd;}techdegree seal-36
Adam Fields
Full Stack JavaScript Techdegree Graduate 37,838 Points

You can definitely pass an array of Towers, and also make them private:

public class Level {
  private readonly Invader[] _invaders;
  private readonly Tower[] _towers;

  public Level(Invader[] invaders, Tower[] towers) {
    _invaders = invaders;
    _towers = towers;
  }
}

Or you can set them after instantiation:

public class Level {
  public Invader[] Invaders { get; set; }
  public Tower[] Towers { get; set; }
}

Level level = new Level {
  Invaders = invaders,
  Towers = towers
}

The original example was demonstrating Object Initializers.

Using the initializer syntax makes writing your class easier with less boilerplate (you don't need to write the parameterized constructor with a bunch of assignments). On the other hand, that's not how we do it in Java and JavaScript, so it's one of those C# tricks you have to remember when switching languages.

You should pick one way or the other, though. Setting one property in the constructor, and initializing the other using a an initializer is confusing, in my opinion.