project-error-handling VS rust-cpython

This actually is an example of where the compiler errors could (or should have) maybe provided more help or even the potential solution, it might be worth submitting this to the error handling group.

If anyone's interested in helping to shape the future of Rust's built-in error-handling story, there's an error handling project group that's been doing great work recently, e.g. the major effort to move the Error trait into libcore ( https://github.com/rust-lang/project-error-handling/issues/3 ) and stabilizing std::backtrace. You can follow along or get involved via the #project-error-handling channel on the Rust zulip: https://rust-lang.zulipchat.com/

Getting it into alloc would enable usage in a LOT more contexts, like WASM and kernel code. Does this need a distinct tracking issue outside the ticket for moving it to core or would that just add more administrata?

without trolling https://github.com/rust-lang/project-error-handling exist and is far from having strong conclusion and anyway I will always favor enum Error anyway however I like the idea to have a opaque box in the enum for "this is a opaque error you can't deal with as a user of my api"

IIRC, the Error Handling Project Group is aware of these ideas. If this kind of thing interests you and you want to contribute, you should look into getting involved with that group.

> you should have the underlying message of the std::io::Error

This is a point of debate[1] among the error-handling working group.

[1]: https://github.com/rust-lang/project-error-handling/issues/4...

Focusing on good error messages has permeated throughout the community. There's even the Error Handling Project Group if you weren't convinced how committed the language designers are to getting this right. There are a number of techniques we can use to make our errors more informative. Along the way, we will discuss the crates that can help.

The Error Handling Working Group is looking at potential breaking changes for embedded users. Maybe you could work within that group?

I've never used pyo3, just cpython, but the latter at least let me do things like:

And don't forget https://github.com/dgrunwald/rust-cpython to complete the circle

For interoperating with Python, check out PyO3 or rust-cpython. (More generally, see Rust Interop and Are We Extending Yet?)

You probably should learn Rust. Aside from the process of learning new and different languages making you a better programmer, rust-cpython, PyO3, or Interoptopus make it easy to expose Python APIs from your Rust code. (eg. So it's easy to compile the same codebase as both a Python module and a WebAssembly module.)

Have you looked into abi_stable, flapigen, interoptopus, cbindgen, PyO3, or rust-cpython?

Personally, I'm not willing to compromise on my GUI look and feel, so I use PyQt or PySide to write my GUIs against the QWidget API (I'm a KDE user and Python is the only language with mature memory-safe bindings to Qt) and, if the project can be structured with a frontend-backend separation, I use rust-cpython or PyO3 to write a backend in Rust that the Python frontend can import. Sort of using Python/Rust as a QWidget analogue to the QML/C++ architecture promoted for Qt Quick. (Which I don't use because it's still too incomplete on Kubuntu 20.04 LTS.)

also, check out rust-cpython, PyO3, and maturin, among other things. They're really nice options for using Rust for its strengths and Python for its strengths within the same project.

This section uses flapigen to expand the foreign_class macro into many cpython functions as an extension module, and cargo compiles it as a cdylib. If you want to see what that looks like, install cargo-expand and run cargo expand. You'll get a lot of generated rust code.

For Python specifically, In addition to using rust-cpython or PyO3, maturin makes it really comfortable to build, package, and publish Rust code into Python packages and, if your niche doesn't quite fit, there's setuptools-python which might do it.

hlua or rlua are what you want for Lua, rust-cpython or PyO3 for Python, rutie for Ruby, and possibly deno_core for JavaScript.