Type annotations and dynamic checking for a tensor's shape, dtype, names, etc. (by patrick-kidger)

Torchtyping Alternatives

Similar projects and alternatives to torchtyping

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better torchtyping alternative or higher similarity.

torchtyping reviews and mentions

Posts with mentions or reviews of torchtyping. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-02-11.
  • [D] Have their been any attempts to create a programming language specifically for machine learning?
    12 projects | /r/MachineLearning | 11 Feb 2023
    Not really an answer to your question, but there are Python packages that try to solve the problem of tensor shapes that you mentioned, e.g. or
  • What's New in Python 3.11?
    14 projects | | 26 Jun 2022
    I disagree. I've had a serious attempt at array typing using variadic generics and I'm not impressed. Python's type system has numerous issues... and now they just apply to any "ArrayWithNDimensions" type as well as any "ArrayWith2Dimenensions" type.

    Variadic protocols don't exist; many operations like stacking are inexpressible; the synatx is awful and verbose; etc. etc.

    I've written more about this here as part of my TorchTyping project: [0]


  • Can anyone point out the mistakes in my input layer or dimension?
    1 project | /r/learnmachinelearning | 6 Jun 2022
  • [D] Anyone using named tensors or a tensor annotation lib productively?
    2 projects | /r/MachineLearning | 18 Apr 2022
    FWIW I'm the author of torchtyping so happy to answer any questions about that. :) I think people are using it!
  • [D] Ideal deep learning library
    9 projects | /r/MachineLearning | 5 Jan 2022
    The one thing I really *really* wish got more attention was named tensors and the tensor type system. Tensor misalignment errors are a constant source of silently-failing bugs. While 3rd party libraries have attempted to fill this gap, it really needs better native support. In particular it seems like bad form to me for programmers to have to remember the specific alignment and broadcasting rules, and then have to apply them to an often poorly documented order of tensor indices. I'd really like to see something like tsalib's warp operator made part of the main library and generalized to arbitrary function application, like a named-tensor version of fold. But preferably using notation closer to that of torchtyping.
  • [P] torchtyping -- documentation + runtime type checking of tensor shapes (and dtypes, ...)
    2 projects | /r/MachineLearning | 7 Apr 2021
    Yes it does work with numerical literals! It support using integers to specify an absolute size, strings to specify names for dimensions that should all be consistently sized (and optionally also checks named tensors), "..." to indicate batch dimensions, and so on. See the full list here.
  • A note from our sponsor - SaaSHub | 19 May 2024
    SaaSHub helps you find the best software and product alternatives Learn more →


Basic torchtyping repo stats
11 months ago

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives