types

My goal is to have the best documentation for each provided type.

If something is unclear in any of the types, please comment or open a PR to improve it.

Some things you could contribute:

• Fix typos.
• Improved description of the type.
• More examples.
• Provide more real-world use-cases. This helps the user understand where a type might come in handy.
• Add links to relevant discu

Elm has the option to output errors as JSON (via a flag), and something like that is handy for writing tooling around it. I'm trying to integrate pytype into ALE and this would make it a lot easier.

Input

[→ View on sorbet.run](https://sorbet.run/#%23%20typed%3A%20true%0Arequire%20'sorbet-runtime'%0A%0Aclass%20A%0A%20%20extend%20T%3A%3ASig%0A%20%20sig%20%7Breturns%28T.nilable%28T%3A%3AHash%5BString%2C%20Integer%5D%29%29%7D%0A%20%20attr_accessor%20%3Aexample%0Aend%0A%0AA.new.example%20%3D%20%7B%3Afoo%20%3D%3E%200%7D%0A%0A%23%20lib%2Ftypes%2Fconfiguration.rb%3A296%3Ain%20%60call_validat

Add new function utility which is useful in tests:

const createFactoryWithConstrain =
    <Constrain>() =>
    <U extends Constrain>(value: U): U =>
        value;

Playground with use cases – tsplay.dev/Ndo6Yw

With #235 I've noticed that InstanceOf is undocumented in the readme.

I'd like to add a config and the ability to have a .js config file in order to generate nestjs repositories and files that just have types. The easiest way to do this, and without introducing much additional maintenance would be to let folks supply their own generator templates.

Splitting the types to a different library might be a little tricky to add in a config, so at first it might not b

References to typing.TYPE_CHECKING are evaluated at runtime, even though they should be treated as compile-time constants. This can have a significant performance impact within hot functions.

Example:

from typing import TYPE_CHECKING  # Or from typing_extensions import ...

if TYPE_CHECKING:  # This should compile to nothing
    whatever

A lot of the files do not use a type checking block, and thus imports only for typing are imported at runtime - increasing memory usage unnecessarily. The task would be to a flake8 type checking plugin (for example this one) to the .pre-commit-config.yaml file, run pre-commit run --allf-files, and fix all reported issues.

Debugging Kotlin∇ code within IntelliJ IDEA can be somewhat cumbersome due to the functional API structure (lots of deeply-nested stack traces and context switching). To facilitate more user-friendly debugging, we should add support for visual debugging by exposing Kaliningraph’s built-in graph visualization capabilities. For example, the use

What version of Racket are you using?

Racket 8.2.0.8

What program did you run?

(: hi (All (r #:row)
           (-> r r)))
(define (hi a)
  a)

What should have happened?

The type checker should reject the program, because a type variable for a polymorphic row type is in fact only allowed to appear in (Class #:row-var _) in Typed Racket.

If you got an erro

It is common to have Union traits of the form Union(None, <something>). As a convenience to developers, and following a similar convention in Python's typing module, we should consider having Optional(<something>) as an alternative way of writing Union(None, <something>).

An alternative would be to make allow_none metadata universally accepted across TraitType instances.