Valentin Shergin 11439eabfc Fabric: Using #ifndef NDEBUG instead of #ifdef DEBUG ...

Summary:
Trivial.
Apparently, `DEBUG` is non-standard feature and using `assert` with `DEBUG` is practically asking for bugs. So, if your `assert` relies on some variable which is only defined when `DEBUG` is set, it's easy to get invalid code because NDEBUG and DEBUG can be unsync.
So, we have to use clunky double negative `#ifndef NDEBUG` everywhere where we used DEBUG.

Reviewed By: JoshuaGross

Differential Revision: D15031328

fbshipit-source-id: 036f573e68925741ca46384261885766c87db1e3

2019-04-23 15:13:36 -07:00

..

attributedstring

Fabric: Fixing usage of Folly's hash_combine

2019-03-14 18:35:00 -07:00

components

YGStyle: wrap all fields into accessors

2019-04-23 08:12:35 -07:00

core

YGStyle: wrap all fields into accessors

2019-04-23 08:12:35 -07:00

debug

Fabric: getDebugDescription implementation for shared_ptr, weak_ptr and unique_ptr

2019-04-04 12:38:22 -07:00

graphics

Fabric: properly convert prop value with object shape

2019-04-10 11:04:23 -07:00

imagemanager

Consolidate shared_mutex with better::shared_mutex (#24075)

2019-03-21 00:18:33 -07:00

mounting

Fabric: Using #ifndef NDEBUG instead of #ifdef DEBUG

2019-04-23 15:13:36 -07:00

sample

Fabric: Bunch of small changes in ContextContainer

2019-04-16 07:35:07 -07:00

textlayoutmanager

Fabric: Bunch of small changes in ContextContainer

2019-04-16 07:35:07 -07:00

uimanager

Fabric: Introducing MountingTransaction

2019-04-20 10:53:16 -07:00