Element-wise inference via generics #1

New Issue

samgriesemer · 2024-12-13T21:43:52Z

samgriesemer commented

2024-12-13 21:43:52 +00:00

The FormatRegistryMeta meta class infers inheritance hierarchies via subclasses known under mro(), but we still have to explicitly define compositional relationships by explicit elements (the components attribute in the CO3 base class). Inspired from some of the musings in the Resource-Medium realm, we may be able to also infer components by types provided to generics.

The `FormatRegistryMeta` meta class infers inheritance hierarchies via subclasses known under `mro()`, but we still have to explicitly define compositional relationships by explicit elements (the `components` attribute in the `CO3` base class). Inspired from some of the musings in the Resource-Medium realm, we may be able to also infer components by types provided to generics.

samgriesemer commented

2024-12-13 21:43:55 +00:00

For example, in a class B(A), the parent relationship to A is available under B.mro(). But if we define A to be generic, e.g., A[C], subtypes of C can be enforced as the compositional types of inheriting subclasses, e.g., B[D] where D(C). Does mro() give this kind of info? Not sure.

For example, in a class `B(A)`, the parent relationship to `A` is available under `B.mro()`. But if we define `A` to be generic, e.g., `A[C]`, subtypes of `C` can be enforced as the compositional types of inheriting subclasses, e.g., `B[D]` where `D(C)`. Does `mro()` give this kind of info? Not sure.

samgriesemer added the due date 2025-01-10

2025-01-09 07:57:55 +00:00

samgriesemer removed the due date 2025-01-10

2025-01-09 07:58:01 +00:00

samgriesemer added this to the Primary suite (alpha) project 2025-01-11 09:14:53 +00:00

samgriesemer added this to the Medium-resource integration milestone 2025-01-11 09:47:02 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: olog/co3#1