Couldn't occurrence typing catch the error in that example, since evil-atom-reset! can only return an atom wrapping a keyword?
I guess the problem I had is that the "optional typing" moniker seems misleading since it forces you to annotate vars. I had visions of gradually assigning types to vars as it became evident that typing was needed as a pre-runtime guardrail based on how other developers were using my functions. If I'm publishing a library then that's backward thinking, but in a team using core.typed it sounds useful... Only type what you need when you need to. Don't mind me... Clearly I need to actually use the library before developing an opinion. -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
