nimler
pulldown-cmark
nimler | pulldown-cmark | |
---|---|---|
1 | 8 | |
98 | 1,930 | |
- | 1.6% | |
0.0 | 9.0 | |
over 2 years ago | 10 days ago | |
Nim | Rust | |
MIT License | MIT License |
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.
nimler
-
Using Rust with Elixir for code reuse and performance
It's one reason I prefer lighter languages for NIF's. My personal preference is to use Nim and Nimler [1]. It generally compiles quicker than Rust while providing most of the same benefits. To be fair compiling a small Rust library doesn't take too much time. Especially compared to the performance numbers from those Rust NIFs!
1: https://github.com/wltsmrz/nimler
pulldown-cmark
-
CryptoFlow: Building a secure and scalable system with Axum and SvelteKit - Part 3
As a platform that allows expressiveness, we want our users to be bold enough to ask and answer questions with either plain text or some markdowns. Compiling markdown to HTML in Rust can be done via the pulldown-cmark crate. We used it in this utility function:
-
Building a high performance JSON parser
I also really like this paradigm. It’s just that in old crusty null-terminated C style this is really awkward because the input data must be copied or modified. But it’s not an issue when using slices (length and pointer). Unfortunately most of the C standard library and many operating system APIs expect that.
I’ve seen this referred to as a pull parser in a Rust library? (https://github.com/raphlinus/pulldown-cmark)
- Let Rust detect changes in the Markdown file and generate HTML.
-
Show HN: A Graphviz Implementation in Rust
Really glad to see this! Really want an easy way to render graphs in Rust without resorting to the graphiz binary.
What is the current status? Not seeing it listed anywhere, like if there are features that are not supported or if it uses certain layout algorithms but others are desired.
Would you be willing to make a `[lib]` available? I see you have a `lib.rs` but it'd be great if using it didn't require pulling in `[[bin]]` dependencies (you can mark them as optional and mark `required-features` on your bin like pulldown-cmark does [0] or split it into a separate crate in a workspace). It'd also be good to find an available name for the lib and get it published (looks like someone might be squatting on `layout`).
[0] https://github.com/raphlinus/pulldown-cmark/blob/master/Carg...
-
Using Rust with Elixir for code reuse and performance
Author here. I actually was not aware of cmark.ex - thanks for pointing it out.
In this case the code reuse was more important than pure native speed. We already had a Rust library that used pulldown-cmark [1] with some custom tweaks that we wanted to duplicate. Maybe this behavior could have been copied using cmark.ex too (we thought about doing this in pure Elixir, as mentioned in the post), but given how straightforward Rustler made integrating our existing code, this seems like the better choice.
[1] https://github.com/raphlinus/pulldown-cmark
It turned out that making the most popular Elixir Markdown processor, Earmark (originally written by Dave Thomas) and pulldown-cmark, a Rust Markdown processor, produce the same output was going to be difficult. We also required some customization that was not available in both libraries.
-
What are some examples of particularly well written crates?
The crate that's closest to production quality code is pulldown-cmark, but I don't hold it up as an example of well-written code, because it's not particularly easy to understand and there's a lot of very low level code to consume the CommonMark syntax - that helps with code bloat and compile time, but not clarity.
-
What are the Markdown features/extensions enabled in mdbook?
The Markdown processor is pulldown-cmark, which supports these extensions:
What are some alternatives?
cmark - CommonMark parsing and rendering library and program in C
mdBook - Create book from markdown files. Like Gitbook but implemented in Rust
nitter - Alternative Twitter front-end
doctave - A batteries-included developer documentation site generator
efuse_filter - Erlang NIF for Binary Fuse Filter. Fast and Smaller Than Xor Filters.
Rustler - Safe Rust bridge for creating Erlang NIF functions
rust - Empowering everyone to build reliable and efficient software.
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
cmark - 💧 Elixir NIF for cmark (C), a parser library following the CommonMark spec, a compatible implementation of Markdown.
earmark - Markdown parser for Elixir