on Thu Nov 10 2016, Rick Mann wrote:
> Anyway, I'm just curious about the best way to implement this *in Swift* (as
> opposed to say, C++).
As someone who's used both languages extensively, there's nothing in
about this problem that suggests I'd approach it particularly
differently in the two
I'm still just learning Swift, after decades of C++ and Objective-C(++). I've
written entire apps in Swift, but I don't "think in Swift" very well yet. So
I'm looking for advice on what classes, protocols, and extensions might be
"swifty" in this example.
Background
--
I'm working on a
