We'll use TokenSeq for everything, including sequences we expect to contain only one token, mainly for consistency but also so that our local "parser" doesn't need to care about whether the main parser is returning one token or many.
Description
fork of https://github.com/hashicorp/hcl
because issue :
https://github.com/hashicorp/hcl/issues/290
these code permit use of "nested" field decoding which is just composite struct
Languages
Go
83.7%
Ragel
10.2%
reStructuredText
4.4%
Ruby
0.5%
Python
0.3%
Other
0.8%