Skip to content

Support named tuples#284

Merged
arainko merged 4 commits intoseries/0.2.xfrom
named-tuples
Aug 2, 2025
Merged

Support named tuples#284
arainko merged 4 commits intoseries/0.2.xfrom
named-tuples

Conversation

@arainko
Copy link
Copy Markdown
Owner

@arainko arainko commented Aug 2, 2025

No description provided.

@arainko arainko changed the title POC of named tuple support on LTS Support named tuples Aug 2, 2025
type MirroredElemLabels = labels
type MirroredElemTypes = types
}
} if Type.of[A].repr.dealias.typeSymbol.fullName == "scala.NamedTuple$.NamedTuple" =>
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clean this code duplication later on

@arainko
Copy link
Copy Markdown
Owner Author

arainko commented Aug 2, 2025

This doesn't support traversing named tuple fields in configs. It'll come in a follow-up PR

case other =>
Logger.debug(s"Matched an unexpected term")
report.errorAndAbort(s"Couldn't parse an unexpected config option: ${other.show(using Printer.TreeShortCode)}")
report.errorAndAbort(s"Couldn't parse an unexpected config option: ${other.show(using Printer.TreeStructure)}")
Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make this a proper error message later on as well, this is user-scaring level of barf

@arainko arainko merged commit a73df43 into series/0.2.x Aug 2, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant