2467b7139b
* napi procedural macro for basic rust/JavaScript types * introduce the `compat-mode` for `napi` and `napi-derive` crates for backward compatible * remove #[inline] and let compiler to decide the inline behavior * cli now can produce the `.d.ts` file for native binding * many tests and example for the new procedural macro Co-authored-by: LongYinan <lynweklm@gmail.com>
24 lines
798 B
Rust
24 lines
798 B
Rust
use napi::{CallContext, JsObject, JsString, JsSymbol, Result};
|
|
|
|
#[js_function]
|
|
pub fn create_named_symbol(ctx: CallContext) -> Result<JsSymbol> {
|
|
ctx.env.create_symbol(Some("native"))
|
|
}
|
|
|
|
#[js_function]
|
|
pub fn create_unnamed_symbol(ctx: CallContext) -> Result<JsSymbol> {
|
|
ctx.env.create_symbol(None)
|
|
}
|
|
|
|
#[js_function(1)]
|
|
pub fn create_symbol_from_js_string(ctx: CallContext) -> Result<JsSymbol> {
|
|
let name = ctx.get::<JsString>(0)?;
|
|
ctx.env.create_symbol_from_js_string(name)
|
|
}
|
|
|
|
pub fn register_js(exports: &mut JsObject) -> Result<()> {
|
|
exports.create_named_method("createNamedSymbol", create_named_symbol)?;
|
|
exports.create_named_method("createUnnamedSymbol", create_unnamed_symbol)?;
|
|
exports.create_named_method("createSymbolFromJsString", create_symbol_from_js_string)?;
|
|
Ok(())
|
|
}
|