codespan VS inkwell

Having good error messages is one of the important priorities for me in my compiler, so I made the commitment early and am using codespan[0] to report the errors, which is going well so far.

0: https://github.com/brendanzab/codespan

There's https://github.com/brendanzab/codespan as well, and a number linked from their pages.

Working in a GENERAL relational language (ie: not just a query one, like SQL, but general to make full apps, like python/delphi/c# + linq):

https://tablam.org

that is my attempt to resurrect the spirit of the FoxPro/dbase kind of tools.

Is on Rust, and is also my way to sharp my skills on it.

Now, I'm in the process of improve the parsing to be robust like in Rust, so i can show good error messages:

https://github.com/brendanzab/codespan

and also, hopefully, implement a solid type inference that work fine with the challenge of infer joins like "customer CROSS JOIN address".

---

The idea, long-term, is create a tool alike MS Access/FoxPro+Excel that I think could be great for a lot of companies (that are using stuff like "BigData" tools -like hadoop- when them are struggling with more fundamental issues!) and improve the condition of make business apps/analysis.

I already hear some interest when the vision is described in full, and I certain any company that use Excel/Access to deal with data and/or make business apps is anemically served by it.

The alternatives now are only for the cloud, and I instead wanna a local-first/on-premise offering...

Nice error messages (for YOUR lang) https://github.com/brendanzab/codespan or https://docs.rs/ariadne/0.1.3/ariadne/

Secondly, I have learned about LLVM, and I have learned about the Inkwell library on Rust (It's a New Kind of Wrapper for Exposing LLVM (Safely)). Has anyone used this library before? Is this a good practice? Is it suitable for my compiler? Can I write some optimization passes of my own using this library?

I am trying to use the inkwell Rust crate for working with LLVM. In Cargo.toml, I have specified the LLVM version using features = ["llvm15-0"]

inkwell is a great llvm binding for rust and it has an implementation of kaleidoscope

I'm working on a compiler that uses the LLVM wrapper Inkwell for compilation. In order to compile something in inkwell, unless I'm missing something (which I very well might be), you need two structs:

Compiler backends (If building JIT/machine compiled langauges) 1. cranelift 2. inkwell - safe rust wrapper around llvm

Haha small world. I think we go to the same university and I took the same or similar course a few years ago. If somebody hasn't done the work for you, you may have to do some instrumentation yourself depending on what you want to track IMO https://github.com/TheDan64/inkwell is the best LLVM wrapper for Rustland (Python's llvmlite is a bit easier to use though)

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.

safe llvm bindings https://github.com/TheDan64/inkwell

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.