Paul Stadig <p...@stadig.name> writes: >> I think that you are worried about the overhead unnecessarily, though. >> The assert status is checked at macro expansion time. If per module >> switching on and off is what then I would suggest that you build on top >> of the existing assert. >> > > There is a huge performance penalty for Clojure assertions, if you don't > compile them away, and there isn't really an easy way to compile them away. > I know this because I wrote a persistent datastructure in Java and rewrote > it in Clojure comparing their performance (using assertions both times). It > was because of the performance penalty of Clojure's assertions that I wrote > the message to the clojure-dev mailing list (and also wrote my own assert > macro that I could toggle easily).
This is always the problem with theories -- they fall to data. If you have tested and found it to be a serious problem, then I have to accept this. I am, none the less, a little surprised to find that it is such a serious problem. -- -- 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.
