[Webkit-unassigned] [Bug 36527] Need an ASSERT that's enabled in release builds

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=36527





--- Comment #4 from Darin Fisher (:fishd, Google) <fishd at chromium.org>  2010-03-24 08:50:59 PST ---
Can we see some examples of code that would be cleaner with FATAL_ASSERT? 
Maybe that would be helpful in evaluating the need.  I tend to agree that
explicitly calling CRASH is fine, and I don't see the need for a CHECK
equivalent in WebKit.

For reference, the Chromium codebase inherits DCHECK and CHECK from internal
Google code.  Those are part of a standard logging package that everyone at
Gogole uses, and we wanted to make it easy for anyone at Google to hack
Chromium.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.