Search Results for "c call tree"

...Dependency-free so that the runtime library (which is written in pure C) can be embedded in any application. All of Tree-sitter’s parsing functionality is exposed through C APIs. Applications written in higher-level languages can use Tree-sitter via binding libraries like node-tree-sitter or the tree-sitter rust crate, which have their own documentation. To build the library on a POSIX system, just run make in the Tree-sitter directory. ...

Unlike traditional LSM-tree storage engines, SlateDB writes data to object storage to provide bottomless storage capacity, high durability, and easy replication. SlateDB is an embedded storage engine built as a log-structured merge-tree. Unlike traditional LSM-tree storage engines, SlateDB writes data to object storage (S3, GCS, ABS, MinIO, Tigris, and so on).

xleak is a lightweight tool for detecting memory leaks and resource mismanagement in C/C++ programs by tracing heap allocations and deallocations with minimal overhead. It hooks into your program’s allocation functions to observe memory usage patterns, helping developers identify locations where memory was allocated but never freed, which is a common source of bugs and performance issues in unmanaged languages. The tool produces detailed reports that show the call stacks associated with leaked allocations, making it easier to track down problematic code paths and fix them. ...

jlrs is a crate that provides access to most of the Julia C API, it can be used to embed Julia in Rust applications and to use functionality it provides when writing ccallable functions in Rust. Currently, this crate is only tested in combination with Julia 1.6 and 1.9, but also supports Julia 1.7, 1.8, and 1.10. Using the current stable version is highly recommended. The minimum supported Rust version is currently 1.65. Julia must be installed before jlrs can be used, jlrs is compatible...

...The library provides facilities for generating the boilerplate for interacting with the BEAM, handles encoding and decoding of Erlang terms, and catches rust panics before they unwind into C. The library provides functionality for both Erlang and Elixir, however Elixir is favored as of now. The code you write in a Rust NIF should never be able to crash the BEAM. Decoding and encoding rust values into Erlang terms is as easy as a function call. Making a Rust struct encodable and decodable to Erlang or Elixir can be done with a single attribute. ...

...To do this, add a / before the pattern. You may also apply logical operators or combine patterns, for example searching test in all files except json ones could be !/json$/&c/test and searching carg both in file names and file contents would be carg|c/carg.