Skip to content

Are asserts intentionally left compiled in? #14461

Closed
@MSLaguana

Description

  • Version: master

I was investigating perf in node-chakracore, and I noticed that there were a lot of calls to IsExternal. I was surprised to find that it was essentially due to this line: https://github.com/nodejs/node/blob/master/src/env-inl.h#L275

According to https://github.com/nodejs/node/blob/master/src/util.h#L130 ASSERT is enabled unless NDEBUG is defined and I don't see anywhere in the build that sets that. Is this intentional? There is also a CHECK macro which doesn't have the same off switch, so it does seem like asserts are intended to be disabled in release builds.

Metadata

Assignees

No one assigned

    Labels

    buildIssues and PRs related to build files or the CI.c++Issues and PRs that require attention from people who are familiar with C++.performanceIssues and PRs related to the performance of Node.js.questionIssues that look for answers.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions