11:01:16scymtymbeach: you are right. the current behavior is overeager. something like 1 that cannot be a type specifier is parsed as a SUBSIDIARY-ITEM, but symbols and conses are parsed as atomic and compound type specifiers respectively
11:03:01scymtymthis should probably work like forms. for forms, only the outermost form is parsed and nested expressions in evaluated positions are marked as unparsed so that the client can interleave environment-dependent processing with recursive parsing