Type lookup table for generics.
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Python
- Sterne
- 20.6k
- Forks
- 3.3k
- PR-Merge-Kennzahlen
- PR-Kennzahlen ausstehend
Beschreibung
Feature
Assume we have a mapping between types, possibly because there's a method with many overloads that takes an object from the first collection of types, and maps it into an object from the second collection of types.
Then, assume we have a generic for which we have a TypeVar that corresponds with the first type. Then there is a method in this generic that does the transformation and produces a corresponding type.
Right now, it would be possible to type the outcome as a union, but much better would be to statically infer the output type.
TypeLookupTable = {
FromType1: ToType1,
FromType2: ToType2,
FromType3: ToType3,
...
}
T = TypeVar('T', bound=any_type_present_as_a_key_in_that_lookup_table)
@dataclass
class SomeGeneric(Generic[T]):
data: T
def func(self) -> TypeLookupTable[T]:
# This function should produce an instance of the corresponding type of `T` in
# that lookup table.
def func2(self) -> ReturnTypeForFunctionCall[some_function, [T]]:
# This function returns an object for which the return type is
# inferred by looking at the overload of `some_function`
# when called with input `T`.
return some_function(self.data)
Pitch
I'm building a synchronous abstraction layer on top of an async library. This means every type from the async implementation will correspond to a type from the synchronous abstraction. There is one function wrap with tons of overloads that takes an async type and returns the corresponding sync type. (it also takes an anyio.BlockingPortal, but that's not relevant for this issue). There are many approaches for the implementation, the dictionary mapping being the easiest, because runtime introspection of the types in the dictionary is the easiest.
Right now, I can't come up with other examples for situations where it's useful, but I'm sure there are other cases where a generic class calls any of a collection of function overloads and where we want to infer the corresponding return type.
Among the two demonstrated approaches, (ReturnTypeForFunctionCall and TypeLookupTable), I'm mostly in favor of TypeLookupTable, because a collection of overloads can always be expressed using that lookup table. Something like:
def function_with_many_overloads[T](data: T) -> TypeLookuptable[T]: ...
(That would expand to as many overloads as there are mapped types in that table.)
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginne mit der Untersuchung der vorgeschlagenen Formen von TypeLookupTable und ReturnTypeForFunctionCall und ihrer Beziehung zu generischen TypeVars und überladenen Funktionen in Python. Verwende das Beispiel wrap als motivierenden Einstiegspunkt; für den Abschluss ist ein festgelegtes Design zur statischen Ableitung entsprechender Rückgabetypen erforderlich, einschließlich der unterstützten Zuordnung und der Semantik von Überladungen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- python
- Bereich
- devtools
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100