Hello, when using rusty_jsc, I prefer to keep the rusty_jsc namespace (for example, rusty_jsc::JSValue). Most of the time, it works fine, but when using the callback macro, I found that I have to use use rusty_jsc::JSValue in the code. After checking the source code, I noticed that there is a part in the definition of the callback macro that directly uses JSValue (without the rusty_jsc namespace), and the constructor macro has a similar situation. Is there any specific reason for this?
Hello, when using rusty_jsc, I prefer to keep the rusty_jsc namespace (for example, rusty_jsc::JSValue). Most of the time, it works fine, but when using the callback macro, I found that I have to use
use rusty_jsc::JSValuein the code. After checking the source code, I noticed that there is a part in the definition of the callback macro that directly uses JSValue (without the rusty_jsc namespace), and the constructor macro has a similar situation. Is there any specific reason for this?