Self-types in NRoles

Since roles are weaved into target classes, it's sometimes necessary for them to be able to identify the type of these classes.

NRoles supports self-types through the use of a type parameter with the special name S:

public abstract class REquatable<S> : IEquatable<S>, Role {
  public abstract bool Equals(S other);
  public bool Differs(S other) {
    return !Equals(other);
  }
}

To cast this to the type parameter, just use the Cast<T> extension method:

public class Identity<S> : Role {
  public S Self {
    get { return this.Cast<S>(); }
  }
}

When other roles compose roles with self-types, they must flow the self-type through, since it will ultimately be determined by the target classes that compose them:

public abstract class RComparable<S> : 
  IComparable<S>, Does<REquatable<S>>, Role {
  ...
}

The post-compiler will check all classes that compose roles with self-types and issue an error message if the type parameter is not the target class itself.

public sealed class Money : 
  Does<RComparable<Money>>, Does<REquatable<Money>> {
  ...
}

Constraints added to the self-type become requirements for the target classes to fulfill:

public class MyRole<S> : Role
  where S : ISomeInterface {
  ...
}

public class MyClass : ISomeInterface,
  Does<MyRole<MyClass>> {
  ...
}

This way, roles can work with the type of the classes that compose them generically and safely. It's useful, for example, for fluent interfaces that return the type of this, used for fluent method chaining:

public class PropertyBag<S> : Role {
  public S With(string name, object value) {
    ...
    return this.Cast<S>();
  }
}

Comments

Post a Comment

Popular posts from this blog

The Acyclic Visitor Pattern

Knock knock The visitor design pattern is a way to add new operations to a hierarchy of classes without having to change the hierarchy itself. For example, with a simple hierarchy of fruits, you can have an IFruitVisitor interface that operates on the different classes in the hierarchy (in C#): interface IFruitVisitor { void Visit(Apple apple); void Visit(Grape grape); } The hierarchy classes then accept the visitor and fulfil the double-dispatching necessary to call the right Visit method: abstract class Fruit { public abstract void Accept(IFruitVisitor visitor); } class Apple : Fruit { public override void Accept(IFruitVisitor visitor) { visitor.Visit(this); } } class Grape : Fruit { public int NumberOfGrapes { get; set; } public override void Accept(IFruitVisitor visitor) { visitor.Visit(this); } } Note how each Accept method looks the same but is actually dispatching to a different method in the visitor ( Visit(Apple) and Visit(Grape) ). ...
Read more

C# Mixins With State

With the C# quasi-mixin pattern , one of the biggest limitations is that the mixins can't introduce state to a class. An alternative was for the mixin interface to require the composing classes to implement a property that the mixin would use as its own, as demonstrated in this example . In the .NET Framework 4.0, the ConditionalWeakTable<TKey, TValue> class can be used to associate arbitrary state to any instance. It's thread safe and it keeps a dictionary of weak references from the target instance to its associated state. If a target instance has no references outside the conditional weak table, then it can be reclaimed by the garbage collector. When that happens, its entry in the table is removed. This makes it possible for a mixin-like class to maintain state for the instances it extends. Let's look at a mixin for a message container: public enum MessageType { Error, Warning, Info } public class Message { public readonly MessageType Type;...
Read more

Some OO Design

"The critical design tool for software development is a mind well educated in design principles. It is not the UML or any other technology." - Craig Larman I've recently found the following interview question on stackoverflow : Basic sales tax is applicable at a rate of 10% on all goods, except books, food, and medical products that are exempt. Import duty is an additional sales tax applicable on all imported goods at a rate of 5%, with no exemptions. When I purchase items I receive a receipt which lists the name of all the items and their price (including tax), finishing with the total cost of the items, and the total amounts of sales taxes paid. The rounding rules for sales tax are that for a tax rate of n%, a shelf price of p contains (np/100 rounded up to the nearest 0.05) amount of sales tax. This is a very familiar example that can be used as a really good gauge of various software development skills. There are many different ways to solve this problem. ...
Read more