>printf the error and keep going
if ((Nigga)you).AreForReal() {
panic("please")
}
/dpt/ - Daily Programming Thread
Evan Hughes
Asher Robinson
>not seeing what happens to your program when something goes wrong
>ignoring free testing for the sake of soothing your autism
I bet you don't even like empty interfaces
Oliver Evans
Niggo do you even know what you are talking about?
Nolan Jones
Somewhat. Been pounding some go recently.
Usually if something's broken it'll panic anyway, the type checking gets the rest (most) during compile. Errors can be printed or even ignored and it doesn't make much difference, it'll panic at some point, but it can be good to print them for debugging purposes, just like it's good to print any intermediate value before moving on to the next step.
Just my opinion.
Cooper Thomas
That's machete debugging. Eventually you will replace everything with iferr-caca and do error reporting at the top of your call stack no?
Logan Martinez
>Eventually you will replace everything with iferr-caca and do error reporting at the top of your call stack no?
eventually I'll have all my corner cases covered and will just throw errors (and panics) when input is shit.
Obviously this isn't some hardcore giant application, just tooling to automate my personal stuff.
Grayson Harris
Java can't make the console beeps
What is your excuse?
Adrian Garcia
Why the fuck would anyone want to use a Lisp-2?
Bentley Phillips
Why C standard defines datatype as "able to store value as big as X or more" rather than a fixed size?
Jacob Taylor
To support weird and/or old hardware.