Kenta Sato

Printing type names is fixed by #80.

> Edited show method to not show the node.ptr (which includes uninformative/unintuitive pointer memory location number). I do not think pointers are uninformative because they are identifiers in a document...

If you have several node objects in your hand, you can quickly check their distinctiveness by looking at their pointer identifiers. If no pointers shown, you need to manually check...

I do not think that the current way is the best, but I do not think that just removing pointers makes it better, neither. Any suggestions of printing nodes are...

Yes, I plan to do that because properties do not import so many names into the current module. Any objections against it?

But I think using properties looks nice for accessing some properties (e.g., node name) and offering multiple ways to do the same thing is not elegant. So, I concluded that...

I disagree with you. `node.firstelement.prevelement` looks better than `prevelement(firstelement(node))` to me because you don't need to read/write the code from right to left in this case. I think method chaining...

Thank you for reporting a problem. It seems to be a bug of DocOpt.jl. I'll take a look and fix it within a few days.

This and #102 may be related. I think the binaries in the latest release seem to have a serious problem that is not reproducible on my MacBook and CI.

I think it makes sense to liberate the function from the type restriction. What is the type of a value you'd like to pass to the function?