Inkwell Alternatives
Similar projects and alternatives to inkwell
-
-
JetBrains
Developer Ecosystem Survey 2022. Take part in the Developer Ecosystem Survey 2022 by JetBrains and get a chance to win a Macbook, a Nvidia graphics card, or other prizes. We’ll create an infographic full of stats, and you’ll get personalized results so you can compare yourself with other developers.
-
langs-in-rust
A list of programming languages implemented in Rust, for inspiration.
-
-
-
not-yet-awesome-rust
A curated list of Rust code and resources that do NOT exist yet, but would be beneficial to the Rust community.
-
-
SonarLint
Deliver Cleaner and Safer Code - Right in Your IDE of Choice!. SonarLint is a free and open source IDE extension that identifies and catches bugs and vulnerabilities as you code, directly in the IDE. Install from your favorite IDE marketplace today.
-
LiteDB
LiteDB - A .NET NoSQL Document Store in a single data file - https://www.litedb.org
-
parquet2
Fastest and safest Rust implementation of parquet. `unsafe` free. Integration-tested against pyarrow
-
-
llvm-project
The LLVM Project is a collection of modular and reusable compiler and toolchain technologies. Note: the repository does not accept github pull requests at this moment. Please submit your patches at http://reviews.llvm.org.
-
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).
-
-
-
-
-
-
-
-
inkwell reviews and mentions
-
How good is LLVM in other languages other than C++? (In my case I'm interested in using Rust)
I'm currently using the Inkwell bindings for Rust, which I've found actually pretty nice. In terms of generating LLVM IR, the C bindings (which is what Inkwell uses internally) can do anything you want them to (definitely not limited to trivial languages as someone else here said.) I'm even using the LLVM garbage collection infrastructure, with no problems (well, no problems in generating it; the LLVM GC infrastructure works pretty well but is sparsely documented, so actually writing a GC is fairly difficult, but it's doable). The C bindings are actually more stable than the C++ bindings (!), although not quite as stable as the textual IR format; but without the bindings you would have to write code to generate the IR yourself, the compiler would be slower as it must be emitted as text and then reparsed in a different process, and you would have less control over optimization.
-
Are there any repos of tutorials on writing a compiler in Rust?
safe llvm bindings https://github.com/TheDan64/inkwell
-
LLVM Infrastructure and Rust
As we reviewed in this article LLVM IR has many use-cases and allows us to analyze and optimize source code through its passes. Knowing IR language itself will help us to write our passes and build projects around it for debugging, testing, optimizing. Currently, LLVM IR doesn't have Rust API. It's mainly used through the C++ library. However, some user-created repos are available on crates.io. There is a Rust binding to LLVM's C API - llvm-sys and two other, more Rusty APIs that are using LLVM: inkwell and llvm-ir. And finally, if you want to learn how to write a LLVM pass you should start here.
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
The high level crate is called inkwell.
-
What's the best way to generate LLVM code in Rust?
https://github.com/TheDan64/inkwell is about as high-level as it gets (from what I've seen). It's based on top of llvm-sys, which is thankfully kept up-to-date with the LLVM releases.
-
VERY Slow compile times (15s+) with llvm-sys as a dependency
On a side note, there are good high level bindings to llvm-sys, inkwell
-
Can i use rust to write my compiler??
There are also libs that can be used for some tasks like parsing https://lib.rs/parsing and code generation like cranelift https://docs.rs/cranelift/0.76.0/cranelift/ and llvm https://github.com/TheDan64/inkwell
-
Would a functional language like Haskell be worse off in developing a compiler as opposed to a systems language like Rust, C, etc?
You can use any language to make compiler, because all compiled languages are made in itself. But i will use rust/c to make a compiler. Enums in rust is so useful to make ast. I have came across a repo which is a wrapper to expose llvm https://github.com/TheDan64/inkwell . Rust is great for compiler but the because of borrow checker, it is not too good for interpreters. If you really make a working compiler, you will probably rewrite it in your own language. If your are using llvm, cpp or rust are go to choice
-
I was bored, so I built my own programming language
So to use LLVM, all I needed to do was to take my AST and convert it into LLVM IR. I did it using Inkwell the LLVM API in Rust. It is a wrapper around the C API that LLVM has built, and on top of that provides the memory safety guaranteed by Rust. Oh, and this is what LLVM IR looks like in text format (Don't try to understand it, feel it):
Stats
TheDan64/inkwell is an open source project licensed under Apache License 2.0 which is an OSI approved license.
Popular Comparisons
Are you hiring? Post a new remote job listing for free.