emboss/krypt — comment on commit 2e76487ccdeb6a6ae184fe2d8d552f5c98d33998
File:  line 0
By nahi:

Hmm. I changed expecting specs from 'validating at construction and assignment' to 'validate at to_der' at 4aebc7510c330fe0f36acdb9c9530f1691c1b299 because it would be helpful for lazy construction.

```
oid = Krypt::ASN1::ObjectId.new("1.0")
oid.value += "8571.2" if its_asn_oid
```

nil should be allowed from the same reason I thought. Previous spec code is a example how I use 'nil' for lazy construction. Updated spec is using "" and so on as a default value, but I think it's not intuitive...

Strict validation is hard in the language which has mutable String like Ruby.

```
% ruby -Ilib -rkrypt-core -e 'base = "1.0.8571"; oid = Krypt::ASN1::ObjectId.new(base); base << "A"; p oid'
```

Do you think validation at construction and assignment is needed?