Ian Keough

Are you OK if we push this to 0.9?

I think you're right. This is a vestige of of changes that we've made to support the `Opening` type, and we didn't want to break all existing calls to the...

We actually started using `IEnumerable` in Elements, as I like it as a way of "hiding" the implementation, but then I back-tracked to using arrays. I thought having to convert...

It was only half implemented. I've hidden it for now because it wasn't ready for prime time, and I've flagged it for release in 0.2.5.

This is great feedback. What I was thinking (and I'm going to modify the description above based on feedback), was something like this: ```c# var e1 = new Equipment(...); var...

The proposal above has been updated to simplify this around the `IConnection` interface which prescribes an input port and a number of output ports. Are there cases where you have...

@wynged I'd also like to get your input on what properties should be on the `IEquipment` interface. Currently Hypar has a `Properties` collection on `IElement` and I don't like it...

What you've identified with your connection interfaces is something that I think would be really useful generally to represent any kind of connection. Structural connections, room connections, and MEP connections....

Sorry for the delay @wynged. You're correct that the `IConnectedSystem` interface is probably not necessary. You should be able to traverse a system from its root as long as you...

If you did want to make a typed version of a connection system, you could do it like this: ```c# public interface IConnector where T: Element { // The location...