mirror of
https://github.com/denoland/deno.git
synced 2024-10-31 09:14:20 -04:00
b560246f30
<!-- Before submitting a PR, please read http://deno.land/manual/contributing 1. Give the PR a descriptive title. Examples of good title: - fix(std/http): Fix race condition in server - docs(console): Update docstrings - feat(doc): Handle nested reexports Examples of bad title: - fix #7123 - update docs - fix bugs 2. Ensure there is a related issue and it is referenced in the PR text. 3. Ensure there are tests that cover the changes. 4. Ensure `cargo test` passes. 5. Ensure `./tools/format.js` passes without changing files. 6. Ensure `./tools/lint.js` passes. --> |
||
---|---|---|
.. | ||
Cargo.toml | ||
lib.rs | ||
README.md | ||
symbol_exports.json |
napi_sym
A proc_macro for Deno's Node-API implementation. It does the following things:
- Marks the symbol as
#[no_mangle]
and rewrites it aspub extern "C" $name
. - Asserts that the function symbol is present in
symbol_exports.json
. - Maps
deno_napi::Result
to rawnapi_result
.
use deno_napi::{napi_value, Env, Error, Result};
#[napi_sym::napi_sym]
fn napi_get_boolean(
env: *mut Env,
value: bool,
result: *mut napi_value,
) -> Result {
let _env: &mut Env = env.as_mut().ok_or(Error::InvalidArg)?;
// *result = ...
Ok(())
}
symbol_exports.json
A file containing the symbols that need to be put into the executable's dynamic symbol table at link-time.
This is done using /DEF:
on Windows, -exported_symbol,_
on macOS and
--export-dynamic-symbol=
on Linux. See cli/build.rs
.
On Windows, you need to generate the .def
file by running
tools/napi/generate_symbols_lists.js
.