Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Namespace conflicts

See original GitHub issue

Namespaces would conflict and only the latest namespace would be activated at the same time.

Test case:

let debug = require('debug');

debug.enable('test1*');
debug.enable('test2*');

let log_1 = debug('test1');
let log_2 = debug('test2');

console.log(1, log_1.enabled);
console.log(2, log_2.enabled);

Results:

1 false
2 true

Expected:

1 true
2 true

Issue Analytics

State:
Created 6 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

3reactions

TooTallNatecommented, May 2, 2017

@thebigredgeek This is probably another example of how we need to fix enable() / disable() for v3.

1reaction

qixcommented, Jun 20, 2018

@qix-

Top Results From Across the Web

Resolving namespace conflicts - c++ - Stack Overflow

The entire point of namespaces is defeated when you say " using namespace ". So take it out and use namespaces.

Resolving Namespace Conflicts - ADM Help Centers

A namespace conflict of the rename kind occurs when two versions' simple names differ from the simple name of their closest common ancestor...

Handle Conflicting Namespaces with Aliases

Every once in a long while, I have a class name that appears in two different namespaces (there are other kinds of namespace...

2.9 — Naming collisions and an introduction to namespaces

This error is generally referred to as a naming collision (or naming conflict). If the colliding identifiers are introduced into the same file, ......

Namespaces and Symbol Conflicts | C++ Modularity ... - InformIT

Namespaces, which are simple to learn and apply, offer a clever means of packaging your code and can assist when symbol conflicts occur....