This information is used later in the debug tree-building process to rename certain parsers so that they do not end up being named things like "packageanon".
You only need to run this once per parser-holding object.
Can also be used if a more informative name for a parser is wanted. In this case, use this method after using names or lexer to override the automatically collected / found name.
Does the implementation of the collector for the current Scala platform actually work in automatically finding parsers in objects and getting their field names as written in your parser code?
Does the implementation of the collector for the current Scala platform actually work in automatically finding parsers in objects and getting their field names as written in your parser code?
For Scala 3 on the JVM, it is advised that all parsers in objects being introspected are marked public, as otherwise, a semi-deprecated call to setAccessible will be called on a private object, which may be restricted or removed in a future version of the JVM. It may be advised to manually name one's parsers (to be debugged) using assignName or parsley.debugger.combinator.named if that warning is not desirable.