News for hackers. Stuff that matters.
Re:Show HN: Finite State Machine for Go by untothebreach on Thursday September 18, 2014 @08:07AM (#8334755)
I mostly like this. The only gripe I have with it is the stringly-typed way of triggering events. It seems like you might be able to better leverage the type system to ensure that spelling mistakes or fat-fingerings don't cause a runtime error sometime in the future. If the .Event() method took an object that satisfied the "Trigger" (or something) interface, instead of just a string, you might be able to catch those kinds of errors during compile-time instead.
Re:Show HN: Finite State Machine for Go by maxpersson on Thursday September 18, 2014 @08:19AM (#8334790)
Thanks for the feedback! It's a good suggestion, and having something else than strings as events is something that I have analyzed. Currently different handlers depends on string operations as selectors, for example "before_<event>". Any ideas on how to move that to the static type world (preferably without using the reflect package)?