MOZGIII

Results 132 comments of MOZGIII

So far I like where this is going. Using GC and owner references sounds like a great idea. "Namespacing on our own" sounds good too - it's most likely the...

Please take a look at #53 - I think I found a solution to the name resolution issue.

I naively expected `[target.'cfg(…)'.**]` to work for everything. I guess I'd be great to if this was the reality - after if I expected it other people might've too. That...

This is not yet supported out of the box, afaik. Though, we can still come up with a custom workaround! Refs: - https://github.community/t5/GitHub-Actions/Github-actions-Cancel-redundant-builds/td-p/29549 - https://github.community/t5/GitHub-Actions/Is-it-possible-to-cancel-previous-jobs-automatically-when-the/td-p/37139

This #123 is unrelated, and it just fixes a bug.

`continue-on-error` would work for me, thx. I've already switched to a more straightforward solution: a step-level `if` statement. https://github.com/timberio/vector-test-harness-github-actions-test-repo/blob/df67ea9b6f2228a4a1947650e990a4b9a71da163/.github/workflows/test-harness.yml#L12-L16

It's a good idea. There is a certain penalty to the extraction of the fields and building the `metrics::Key`, so we should benchmark heavily to avoid issues. The potential problem...

> Not sure which would be the right way to deal with this: mention the `--root-ca-file` option in the docs, make Vector respect the system TLS trust store or both....

> Personally, I would suggest to rename all setters to `set_my_property` and place the `my_property` getters back in the `impl MyDictionaryType` as conventionally used in Rust. Preferably in another PR...