Ashley Mannix

Hey @qdot! :wave: I haven't worked on this project in a while, but this sounds like something we should be handling transparently so that kebab-case crate names are converted into...

Hi @dbettin thanks for reaching out! This crate is still very immature, right now it's just supporting some toy experiments of mine. I do have some very basic cross-platform support...

I've spent some time thinking about this and have a design a bit like this in mind: # Cross platform ``` $ cargo-nuget cross --target win-x64 --win-x64-path ./out/win/app.dll --target osx-x64...

I've started playing with this and am refactoring out a core input structure we can use to drive commands. There are a few potentially nasty pieces to deal with, like...

Right now I'd like to get: - local builds working the same - cross builds working for well-formed rids - backdoor cross build that stuffs an output in an `any`...

Would also be nice to be able to specify things using a `toml` config. That'll be much easier to parse into the input structure than command-line args. Maybe for the...

Ok we've got some basic cross-platform support built in by specifying the path to a pre-built binary for each target. I think this is the core use-cases because you can...

There's still a bit of cleanup to do before the next release: - newlines in logs are a bit of a mess - remove the deny warnings attribute - add...

I think this should just turf the `enrich` experiment and leverage the already well-tuned `tracing` APIs for context.

Also need to figure out the semantics for macros in cases where the behaviour might be ambiguous: where the same key appears twice: ```rust log!("{a: 42}", { a: "not 42"...