enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-12-26 02:02:15 +03:00
Code Issues Projects Releases Wiki Activity
3e23e72bed
enso/lib/rust/parser/jni/Cargo.toml

23 lines
491 B
TOML
Raw Normal View History

JNI bindings for enso-parser (#3599) Provide a JNI dynamic-library interface to `enso_parser`. # Important Notes - The library can be built with: `cargo build -p enso-parser-jni`. - A new `org.enso.syntax2.Parser` API is implemented on top of the JNI interface provided by `enso-parser-jni`. - We are using the `jni` crate, since apparently Java cannot just call C-ABI functions. The crate is not well-maintained. I came across an obviously-unsound `safe` function, and found it was reported over a year ago, with a PR to fix: jni-rs/jni-rs#303. However our needs are simple. We can't trust any safety guarantees they imply, but I think we are unlikely to encounter any logic bugs using the basic bindings.
2022-07-25 17:24:21 +03:00
[package]
name = "enso-parser-jni"
version = "0.1.0"
authors = ["Enso Team <enso-dev@enso.org>"]
edition = "2021"
description = "Enso Parser JNI dynamic library."
readme = "README.md"
homepage = "https://github.com/enso-org/enso"
repository = "https://github.com/enso-org/enso"
license-file = "../../LICENSE"
[dependencies]
enso-prelude = { path = "../../prelude" }
enso-parser = { path = "../" }
Provide syntax warnings to Java (#10645) Translate syntax warnings and attach to IR when translating operator applications. We should ensure that all Trees are checked for warnings and every warning is attached to some IR. That would require a bit of refactoring: In TreeToIr, we could define helpers wrapping every IR constructor and accepting a `Tree` parameter. The `Tree` could be used to populate the `IdentifiedLocation` when constructing the IR type, and then to attach all warnings after constructing the IR object. # Important Notes - Update JNI dependency. - Introduces a `cargo bench` runner for parser.
2024-07-24 20:54:23 +03:00
jni = "0.21.0"
JNI bindings for enso-parser (#3599) Provide a JNI dynamic-library interface to `enso_parser`. # Important Notes - The library can be built with: `cargo build -p enso-parser-jni`. - A new `org.enso.syntax2.Parser` API is implemented on top of the JNI interface provided by `enso-parser-jni`. - We are using the `jni` crate, since apparently Java cannot just call C-ABI functions. The crate is not well-maintained. I came across an obviously-unsound `safe` function, and found it was reported over a year ago, with a PR to fix: jni-rs/jni-rs#303. However our needs are simple. We can't trust any safety guarantees they imply, but I think we are unlikely to encounter any logic bugs using the basic bindings.
2022-07-25 17:24:21 +03:00
[lib]
name = "enso_parser"
crate-type = ["cdylib"]
Bump Rust Toolchain (#9517) This PR updates the Rust toolchain to recent nightly. Most of the changes are related to fixing newly added warnings and adjusting the feature flags. Also the formatter changed its behavior slightly, causing some whitespace changes. Other points: * Changed debug level of the `buildscript` profile to `lint-tables-only` — this should improve the build times and space usage somewhat. * Moved lint configuration to the worksppace `Cargo.toml` definition. Adjusted the formatter appropriately. * Removed auto-generated IntelliJ run configurations, as they are not useful anymore. * Added a few trivial stdlib nightly functions that were removed to our codebase. * Bumped many dependencies but still not all: * `clap` bump encountered https://github.com/clap-rs/clap/issues/5407 — for now the warnings were silenced by the lint config. * `octocrab` — our forked diverged to far with the original, needs more refactoring. * `derivative` — is unmaintained and has no updated version, despite introducing warnings in the generated code. There is no direct replacement.
2024-03-25 02:45:55 +03:00
[lints]
workspace = true
Reference in New Issue Copy Permalink