Anton Whalley

Results 178 comments of Anton Whalley

FYI As traitobject, unsafeany and typemap are unmaintained I've pulled https://github.com/philip-peterson/destructure_traitobject/ into unsafe-any here https://github.com/No9/rust-unsafe-any/commit/e0c79e23f0265597f6ab92b296296ff6f474e174 and updated typemap here https://github.com/No9/rust-typemap/commit/f15452a41e34ecdee89852b7727a0cac221ef3e7 I've then pulled typemap into a fork of log4rs here...

Happy to publish these to crates.io I'll look at it over the weekend and update my fork. I can take the maintenance for the short/medium term but I think it...

Dependency repos have moved to orphanage-rs with some additional housekeeping done (clippy/fmt/CI). https://github.com/orphanage-rs/rust-unsafe-any https://github.com/orphanage-rs/rust-typemap Crates published and invites sent to @pinkforest and @estk https://crates.io/crates/unsafe-any-ors https://crates.io/crates/typemap-ors I've PRd updates to this...

Love it!! I am a big fan of this exploratory style of tutorial. Especially the "it's not doing what was expected this is how we fix it". If I could...

My idea is line with what @RafaelGSS suggested. The journey should define a common use case (something that is likely to happen in the real world) to highlight the benefits...

Thanks @mhdawson for the ping. This seems like a good thread to provide a quick update. 1. CI is now back to green https://github.com/nodejs/llnode/actions/runs/2721848039 2. There has been further work...

@RafaelGSS Good suggestion on taking a slot in diagnostics meeting - I'll look out for the next session. @kvakil Agree with the incremental maintenance being hard. I'll try and get...

@Qard @tony-go @kvakil Looks like the Diagnostics session is tomorrow https://github.com/nodejs/diagnostics/issues/574 sorry for the short notice but only just found out. I'll probably attend the one after too if you...

As agreed in the diagnostics meeting I said I would take a look. To me https://github.com/nodejs/diagnostics/issues/349#issuecomment-591657623 from Chris is a good summary. Specifically the point on there being no schema...

In general global installs should not be forced with `sudo` Here is the npm article on your options - https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally I generally prefer the manual option but YMMV https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally#manually-change-npms-default-directory