Charles Samborski

The `emit_error` method on `Serializer` accepts a `&(dyn std::error::Error + 'static)` so the error still needs to be static; but you can indeed pass shorter lived references. Since `ErrorValue` takes...

I prefer to not duplicate the `--no-color` detection here. The most reliable solution is to not use colors directly in `gulp-tslint`, but instead rely on `fancyLog()` and `fancyLog.error()`.

If/once the [record and tuple](https://github.com/tc39/proposal-record-tuple/) support lands, narrowing based on a native tuple length should become possible.

I would prefer a pure Rust verrsion for compatibility with Wasm. For now, I'm able to use `nalgebra_lapack` but I get slightly different results between `nalgebra_lapack`, `ndarray-linalg` and custom code...

Are you talking about tagged commits? I guess the author could tag the commits were he bumped the package version. The main source truth for releases aren't tagged commits but...

I expect `cross metadata` and `cross build` to use the same target directory. I may be missing something, but if `cross metadata` returns `/target`, then why are the events sent...

Taking a step back, my issue is that I want to retrieve the path of the binary after `cross build` has finished and avoid hard-coding if possible. What's the best...

We are encountering the same issue (for the same use case) in c8. Thinking about it, I think that the most reliable solution would be to not use wrapper modules...

I implemented a way to intercept spawn calls and dynamically replace the arguments. Still WIP, but you can check [this commit](https://github.com/demurgos/spawn-wrap/commit/18d477ee335489ca9cb05e70b95b38d3d209e50b). Here is a usage example: ``` spawnWrap .observeSpawn(process.execPath, [NESTED_SYNC])...

Continuing the discussion about durations from https://github.com/chronotope/chrono/issues/954#issuecomment-1717704248 > > This brings me back to the meaning of adding `chrono::Duration::hours(5)`. Is it "add `18,000` historical seconds" or is it "add `18,000`...