Robin Lambertz

I have a branch where I moved to using cargo metadata. It isn’t well tested though. If you want to try it, try to install the cargo-metadata branch of cargo-travis.

AFAIK it already works. Unfortunately, I'm not really using this project anymore, so there isn't much dogfooding going on. I'll try taking it for a test run to make sure...

@spacekookie this is a different issue. For what you're talking about (the fact we have to build kcov and this crate), look at #11 and #17. Basically the solution is...

#52 would help but not fix this. While using the same cargo version brings us a step closer to being able to reuse artifacts, it is still not possible yet...

The nightly failure can probably be fixed by updating the time dependency, with `cargo update -p time`. The 1.70 failure, I'm not sure. Might be worth updating the smithy crates,...

Getting bit-accurate signature seems impossible - signatures include timestamps and other pieces of random data. Even running codesign twice on the exact same binary gives a different binary output AFAICT.

> I don't have any particularly good docs on __entitlements, aside from chapter 5 of book 3 of *OS internals, which goes into code signing in general very in-depth. I...

Actually, this is impossible because of https://github.com/dtolnay/proc-macro-hack/issues/15. Proc Macros are going to be stabilized on 1.30, but they won't be able to expand to expressions. Furthermore, this proc macro would...

https://github.com/roblabla/power-assert-rs here's a WIP port to Proc Macros 1.30. It has several problems: - It hits https://github.com/alexcrichton/proc-macro2/issues/110 - It uses a doc hidden'd function from proc_macro2: `Span::unstable()`, in order to...

There’s a PR open to recover the raw string of a Span: https://github.com/rust-lang/rust/pull/55780. It will be feature gated behind proc_macro_span. Once it lands, I’ll update my fork, and it’ll likely...