Julian Samaroo

This probably needs to be documented better, but you now need to make sure you load Colors.jl manually (via `using Colors`) to get access to the `show_plan` implementation.

Now that #468 is merged, we have `Dagger.show_logs` and `Dagger.render_logs` - see the documentation (https://juliaparallel.org/Dagger.jl/dev/logging-visualization/#Logs-Visualization) for how to use these.

As discussed on Slack, we want to support 1.7+ for the time being.

@findmyway sounds great to me!

@Roh-codeur sorry for the delay; can you give an example of how you would do this without Dagger? So that I have something to look at to understand what you're...

Hi @Roh-codeur ! Thanks for the kind words :smile: The `GraphPlot` is still a work-in progress, because I'm not a d3.js expert. If you have JS and d3 experience and...

This PR is mostly good-to-go, however there is one aspect I'm not happy about: all nodes *must* spawn all the same tasks in the same order, or else we get...

Regarding composability, I think the first "obvious" thing to do is to implement our callback with `Threads.@spawn` (or `Threads.@threads`, if it makes more sense) to spawn BLAS jobs, by default....

If we just wanted to feed in a `Module` and get access to target-specific passes after standard Julia optimizations, would this work? I'm thinking we could run it pretty close...

Please feel free to file a PR to bump compat if it's blocking your work :slightly_smiling_face: