Skip to content

Come up with a better abstraction for looking through Typedef inner types #1142

@bolt12

Description

@bolt12

Is that really the case though? This does a single lookup; shouldn't we recursively look through? What if we get another typedef? Or does that not matter here? I feel like some kind of "unfold typedefs" function, perhaps with an explicit argument indicating whether we want to "unfold all the way" or "just one later" would be good.

Originally posted by @edsko in #1139 (comment)

Metadata

Metadata

Assignees

Labels

ongoingIssues currently actively being worked on.priority: mediumrefactorInternal refactoring

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions