Matt Bauman

Ah, interesting. Do you think this is beneficial? I've been trying to understand their comparator plugin architecture to setup custom comparisons, and then we could fine-tune this behavior for dates...

Is this with regards to a specific implementation? The fields used are easily configurable with the YAML files. In the example dataset and configuration provided in this repository, we specify...

Yes — obviously there's not much we can do about the general case without a huge reworking. But inside the `@everywhere` macro there could definitely be special support for this......

When you do a `t = @distributed for`, you get back a task. The task's value is always `nothing` after all the workers come back. You can explicitly make sure...

Yes, `@distributed` still requires indexing — it'd indeed be good to document this requirement. Note that distributing such a large array to your workers may swamp the computation time with...

Yes, that's correct. Just as a breadcrumb, with https://github.com/JuliaLang/julia/pull/32310 we could possibly add indexing support.

This looks like it updates and replaces #35675? Does it work around the [problem of the mutable Ref](https://github.com/JuliaLang/julia/pull/35675#issuecomment-818051859)?

I mean, I'm all for this, but we should know what the tradeoffs are and make an intentional decision that the good outweighs the bad. @KristofferC do you have a...

What's the status of tooling support here? I'd say that's required before we make any such proclamation.

I'd be okay with a descriptive warning without there being tooling support. I don't like having a prescriptive admonition without tooling support. With tooling support, I'm 100% for it (hence...