Niklas Saari

> @Nicceboy I would also recommend making a draft PR to rasn that adds it, that way people can test it and make PRs to it. Sure, I would like...

One worrying thing currently is the dependency of `bitvec` crate. The future of the project seems uncertain and I noticed the marked issues. I wonder if I should use just...

> For now I would continue with the using bitvec, I have no intention right now to switch from it. It would be a lot of extra work for little...

Maybe you are right, I will use the `bitvec` for now. Here is the comment (README.md) of the author about the situation: https://github.com/myrrlyn

Seems like negative `discriminant` values for custom enumerated values are currently unsupported. OER encoding makes possible to also encode/decode these, and ASN.1 itself does not forbid these. Only positive values...

Is it possible to declare `BitString` type as "NamedBitList"? Seems like encoding can depend on that in the case of OER. In my understanding it might not be currently possible.

I have a problem with interpreting the standard if this is a problem for OER... I might need to set "NamedBitList" as default behavior if it is. I don't have...

One thing which took me a lot of time how to figure out, was how the `field_bitfield` actually worked in UPER. On every trait method, there was call for `self.set_bit(tag,...

Am I understanding correctly that ```asn A ::= SEQUENCE { a BOOLEAN, ... } ``` Is identical to this? ```rust #[derive(AsnType, Clone, Debug, Decode, Encode, PartialEq)] #[non_exhaustive] struct Sequence1 {...

When encoding `SET`, did you try any other way than storing the output to another variable (`set_output`)? I think I have finished everything but `SET`, but now it seems that...