Comments on: Why to Not Use the System Diagnostics Assert Methods https://intellitect.com/blog/dont-use-the-system-diagnostics-assert-methods-unless/ Complex Software Development - Simplified Sun, 18 Sep 2022 12:28:34 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: Tony https://intellitect.com/blog/dont-use-the-system-diagnostics-assert-methods-unless/#comment-389072 Sun, 18 Sep 2022 12:28:34 +0000 http://mark.michaelis.net/Blog/DontUseTheSystemDiagnosticsAssertMethodsUnless.aspx#comment-389072 IL2CPP keeps Debug.Assert around even in release and master mode just as this article claims. If you switch to Mono it will be removed.
At least those are my findings from some testing.

Find and Replace “Debug.Assert” with “// Debug.Assert” and you’ll see it can have a huge performance impact in some cases.

Strangely enough I could not see any difference between Assert, AssertFormat and interpolated strings. It seems calling the Assert function in itself is expensive – with or without fancy strings. But I haven’t tested that any further.

This article recommends using exceptions. However for code that gets called frequently having that extra branch in there isn’t what we want.
My solution was to use #if DEBUG .. #endif around the asserts. Problem solved.

]]> By: Siarhei https://intellitect.com/blog/dont-use-the-system-diagnostics-assert-methods-unless/#comment-123 Tue, 25 Mar 2008 09:50:54 +0000 http://mark.michaelis.net/Blog/DontUseTheSystemDiagnosticsAssertMethodsUnless.aspx#comment-123 In a production code we can allow to ourselves inefficiency by adding assertions.

From "Code complete" by McConel

]]> By: Michael Freidgeim https://intellitect.com/blog/dont-use-the-system-diagnostics-assert-methods-unless/#comment-122 Fri, 20 Apr 2007 06:47:49 +0000 http://mark.michaelis.net/Blog/DontUseTheSystemDiagnosticsAssertMethodsUnless.aspx#comment-122 Did you mean:
"will not even call ReallyLongRunningMethodThatReturnsBool() when DEBUG is NOT defined."?

]]>