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

Parallel graph & nested exceptions #85

Open
gfredericks opened this issue Feb 2, 2015 · 1 comment
Open

Parallel graph & nested exceptions #85

gfredericks opened this issue Feb 2, 2015 · 1 comment

Comments

@gfredericks
Copy link
Contributor

Haallooooooo,

I've been using par-compile and every time it crashes I get my exception wrapped up nicely in 6 ExecutionExceptions hoo ray!

Should par-compile maybe use modified futures that unwrap exceptions? I'm not sure exactly how to do this, but if we can figure out a clean way is it a good idea? Should we leave one wrapper just for funsies?

@w01fe
Copy link
Member

w01fe commented Feb 2, 2015

par-compile was really just meant as a demonstration -- it's suboptimal in a bunch of ways, not least that it creates one thread for each node, which is why you see so many levels of nesting. It might be worth looking at the experimental async compile, which does more appropriate scheduling and should be adaptable to the parallel use csae.

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