c++ Is assert evil?

The Go language creators write^*:

Go doesn't provide assertions. They are undeniably convenient, but our experience has been that programmers use them as a crutch to avoid thinking about proper error handling and reporting. Proper error handling means that servers continue operation after non-fatal errors instead of crashing. Proper error reporting means that errors are direct and to the point, saving the programmer from interpreting a large crash trace. Precise errors are particularly important when the programmer seeing the errors is not familiar with the code.

Surely they're being faggots, right?

______________________________
^* http://golang.org/doc/go_faq.html

>>36
and, btw, these guys talking about replacing `if`s with dispatchers, that is just a form of limited pattern matching. The same stuff parsers, like bison, do.

>>40
``->'' is his/your ``if''.

>>41
It doesn't always work, but it's an obvious thing to do.

>>42
`->` could be a table lookup. Like in {0->'a; 1->'b; 3->'c}. Or it could be a method, like in

class C a=1 b=2 m:{-> a+b}

>>43
Enjoy having your parser dealing with the halting problem when parsing (http://www.perlmonks.org/?node_id=663393) your DSL when it will grow even more.

>>44
implying he has a parser
Oh, /prog/, you are so funny

>>45
implying
Enjoy your new home: http://boards.4chan.org/g/.

implying he has a parser
Even a recursive descent parser is a parser. Even a stupid code walker must do some parsing. Infix notation needs a parser aware of the operators' precedence.

>>46
Yes, RDP is a parser. But that's irrelevant since
wannabe-lisper-12yo-autistic-boy has no parser at all.

Now.
I have a question.
How do you say wannabe-lisper-12yo-autistic-boy in official /prog/ langauge?

risuperu naritai jyuu ni sai autismo no otoko no ko kun? Damn, that's long.

PARSE MONADS EVERYDAY

For that refreshing dead dog

>>47
auchisumu
FTFY