After documenting Issue #5 it seemed sensible to change the connections: Vec<direction> to a Set, presumably a HashSet. This is because a Feature only every touches a direction once. Future expansions may bring rule changes (e.g. a road that loops back on itself in one tile?) but let's not pre-optimise for this.
After documenting Issue #5 it seemed sensible to change the
connections: Vec<direction>
to a Set, presumably a HashSet. This is because aFeature
only every touches a direction once. Future expansions may bring rule changes (e.g. a road that loops back on itself in one tile?) but let's not pre-optimise for this.