Pierre Chifflier

Hi, Thanks for your contribution! First of all sorry for the long delay in the reply. This crate was under heavy refactoring to merge/use parsing code from the new `asn-rs`...

I would love to see that at build time, but I don't think there is a way to resolve a symbol value in a proc-macro (or macro). Maybe #45 is...

Hi, Thank you for the PR. However, I'm not sure setting the `Header` lifetime to the input's is required: in those functions, the header is only used, not stored, so...

Is it using everything from `cargo`, or debian packages? I've already heard of this error, but I have no diagnosis for the moment. It seems related to the rust compiler...

Ok, I was able to reproduce the problem on a fresh Debian 10 install. I also suspect a bug in the Debian version of cargo/rustc. On the same host: -...

The side-effect is that crates using `der-parser` (like `x509-parser` will probably fail to build), but other than dependencies, this has no side effect on `der-parser` itself. OTOH, this also seems...

Hum, github closed by because of commit message of the possible fix. Until confirmation that bug is really fixed, I'm reopening this

After merging #18, things have changed since `Oid` now has `Eq, PartialEq, Clone`. So, you can match an `Oid`: ```rust assert_eq!(oid, oid!(1.2.840.113549.1.1.1)); ``` However, as explained, this cannot be used...

Great, thanks @jannschu !

That looks interesting. I made a quick test, but Rust 1.45 still complains ```rust match oid { oid!(1.2.840.113549.1.1.1) => true, _ => false, } ``` gives the following error: ```rust...