@anandabits Interesting. I see the FooAction struct calls .foo(), and BarAction call .bar(). Is that required? (struct per message?)
-
-
- View other replies
-
.
@mpweiher also note that there are many potential avenues for automatically synthesizing the boilerplate in the future -
@anandabits How about not having the boilerplate in the first place? ;-) - View other replies
-
@mpweiher it also eliminates the need for boilerplate dynamic checks (as shown in this post by@wilshipley http://blog.wilshipley.com/2016/05/pimp-my-code-book-2-swift-and-dynamism.html …) -
@anandabits@wilshipley Well, the asserts are somewhat pointless, and just go to show that the metasystem isn’t quite good enough yet. … - View other replies
-
@anandabits@wilshipley … However, I don’t see how the solution to small amounts (but too much!) boilerplate is MORE boilerplate? Instead… - View other replies
-
@anandabits@wilshipley …I would look at ways of eliminating the remaining boilerplate, and dynamic systems tend to allow end-users to at … - View other replies
-
@anandabits@wilshipley …least give it a try, rather than waiting like sheep for big compiler owner to provide a magic solution. YMMV. - View other replies
- Show more
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Matthew Johnson
Marcel Weiher