Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: add some task to github todo #6

Open
dzmitry-lahoda opened this issue Oct 21, 2024 · 3 comments
Open

chore: add some task to github todo #6

dzmitry-lahoda opened this issue Oct 21, 2024 · 3 comments

Comments

@dzmitry-lahoda
Copy link

if any improvement needed, please add some tasks to github?

@purplesyringa
Copy link
Member

For transparency:

I'm currently working on a custom performant stack unwinder. It's supposed to significantly increase the performance of the error path, as well as lead to simplification of the #[iex] API. At the moment, my main goal is to get this unwinder released, tested, and then integrate it into iex.

After that, iex is to be extended to support multiple backends. Namely, it should work with the unwinder disabled, relying on Rust panics (almost like it works now), but also with panic = "abort" by downgrading to Result.

@dzmitry-lahoda
Copy link
Author

dzmitry-lahoda commented Oct 30, 2024

I have other question, does it work with tokio runtime? As I see by design using set_hook/catch_unwind with whatever design does not handle tokio runtime well, until manual integration with tokio is done.

Does iex needs special integration with tokio runtime (specifically how it manages context switching of its thread pool) and thread aborts?

@purplesyringa
Copy link
Member

As far as I can see, iex should work with tokio just fine, as it doesn't utilize set_hook. I haven't tested that yet though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants