reduze VS marker

Compare reduze vs marker and see what are their differences.

reduze

Zig program reduction is upstream in compiler due to various parser + formatter interactions. (by matu3ba)

marker

An experimental linting interface for Rust. Let's make custom lints a reality (by rust-marker)
InfluxDB - Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
reduze marker
1 2
0 138
- 1.4%
10.0 9.4
about 1 year ago 5 months ago
Zig Rust
- GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

reduze

Posts with mentions or reviews of reduze. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-25.
  • Blog Post: Next Rust Compiler
    7 projects | /r/rust | 25 Jan 2023
    If not: Editing the source file may lead to silent formatting jumps, which invalidate your AST. This rules out in-memory AST patching and any tracking of how the AST has been modified (you need to track AST to source locations for that). I've written about that in my another very unfinished reduction project.

marker

Posts with mentions or reviews of marker. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-25.
  • Blog Post: Next Rust Compiler
    7 projects | /r/rust | 25 Jan 2023
    Check out this, which aims to implement said stable interface!
  • 1Password releases Typeshare, the "ultimate tool for synchronizing your type definitions between Rust and other languages for seamless FFI"
    14 projects | /r/rust | 22 Nov 2022
    Hey, I might be able to give some input how I deal with it in [rust-linting](https://github.com/rust-linting/rust-linting). For some context, the project needs to load several dynamic libraries and provide each of them with an abstract syntax tree. Serializing and deserializing the types for every step would most likely be too expensive. That's why I opted for a Rust <-> Rust FFI. There are two parts of this: 1. The loaded libraries needed to accept data from a driver. For this, I generate functions in the library crates which are marked as `extern "C"` and only use FFI safe types. Passing information to the loaded crates then always calls the generated functions, which intern call access a thread local struct instance in the dynamic crate. It's important that the instance implement a specific trait. For the library creation, it seems like magic. 2. Callbacks. The loaded libraries need to pass information back to the driver. For this, I use a struct with function pointers. These are also marked as `extern "C"` and need to only use FFI safe types. The definition of FFI safe, is a bit difficult. Slices, `str`, `Option<>` and most of the rusts STD types don't have a stable layout to the point, that it can change between compilations with the same compiler. Therefore, it's required that each passed type is `#[repr(C)]`. Options are wrapped in an enum, which has `#[repr(C)]`, slices and strings are dismantled into a data pointer and a length. On the receiving and they're reconstructed again. A small warning. I'm not an expert on FFI interfaces. My implementation would probably have some problems with lifetimes, if I'd use a slightly different memory model. So far, this has worked well (Besides the required boilerplate). The project is currently sadly lacking documentation, as it's still under heavy development. If you want, feel free to lock around the code base. The stable types and most of the interface is inside the `linter_api` crate.

What are some alternatives?

When comparing reduze and marker you can also consider the following projects:

rfcs - RFC process for Bytecode Alliance projects

design

bifrost

wasmtime - A fast and secure runtime for WebAssembly

serde-reflection - Rust libraries and tools to help with interoperability and testing of serialization formats based on Serde.

buck2 - Build system, successor to Buck

stklr - STKLR is a tool to help you automatically link up named stuff in your rust docs!

evcxr

crates.io - The Rust package registry