Mingwei Samuel

feat(hydro_deploy): support profiling on windows via `blondie_dtrace`

1

https://github.com/nico-abram/blondie/

[hydro_deploy/core/src/hydroflow_crate/build.rs](https://github.com/hydro-project/hydroflow/pull/1334/files/4c7b8ef3ad426e366b94e972cadddeb4e204aa52#diff-f45308471f074108ebf7d751030176b50c9603e0ca922a934c926e0e78191ff4) Eventually we should probably use a hash; nanoid is a pretty hacky solution since we could even have collisions. _Originally posted by @shadaj in https://github.com/hydro-project/hydroflow/pull/1334#discussion_r1676225033_

- What kind of throughput are we getting - (source or sink op id, tick, bytes, messages), time elapsed per tick Actual work for the network handling may show up...

`LatticeBimorphism` trait should be modified to support references instead of just owned values, to avoid unnecessary `clone()`ing

1

Or multiple traits Or modify `lattice_bimorphism()` hydroflow operator to use `&'lifetime Input` as the bimorphism type parameters

Would be at cool if at some point we can have commented markers in the code for different snippets so line numbers don't go out of sync. _Originally posted by...

> Should we turn the responsibility around to the operators? The operator should tell this part of the code what interests it. > > In other words. Should there be...