feat: Capture generic parameter of an implementation, if there is one #18

Closed
opened 2023-10-17 22:21:22 +00:00 by glen · 2 comments
Owner

Right now, that info is thrown away. But it is there at the front of any generic implementation, typically <T>. So we might as well parse it and capture the generic parameter, which we can recognize later on as need be. That will set us up if we ever need to use a generic parameter other than T or if we ever need more than one.

Right now, that info is thrown away. But it is there at the front of any generic implementation, typically `<T>`. So we might as well parse it and capture the generic parameter, which we can recognize later on as need be. That will set us up if we ever need to use a generic parameter other than `T` or if we ever need more than one.
glen added the
enhancement
label 2023-10-17 22:27:37 +00:00
Collaborator

In 6bfd06cafb I've added code to extract the generic parameter from the reflectedType.

In https://code.studioinfinity.org/glen/typocomath/commit/6bfd06cafb29749542f835a08ccc54fbbba049ba I've added code to extract the generic parameter from the `reflectedType`.
Author
Owner

Looks fine to me. Closing.

Looks fine to me. Closing.
glen closed this issue 2023-10-18 17:18:02 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: glen/typocomath#18
No description provided.