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

e.g.

# map.py
def func(a: int) -> float:
    return float(a)

map(func, ['str'])

$ pytype map.py
Computing dependencies
Analyzing 1 sources with 0 local dependencies
ninja: Entering directory `/[redacted]/.pytype'
ninja: no work to do.
Success: no errors found

while

$ mypy map.py
map.py:5: error: Argument 1 to "map" has incompatible type "Ca

Input

[→ View on sorbet.run](https://sorbet.run/#%23%20typed%3A%20true%0A%0Aclass%20NoShow%20%3C%20BasicObject%3B%20end%0A%0Aclass%20Tests%0A%20%20def%20self.test_each(tests%2C%20%26blk)%3B%20end%0A%20%20def%20self.describe(%26blk)%3B%20end%0A%20%20def%20self.it(%26blk)%3B%20end%0A%0A%20%20describe%20%22foo%22%20do%0A%20%20%20%20test_each%20%5BNoShow.new%5D%20do%20%7Cns%7C%0A%20%20%20%20%2

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

These operations related to bytes values are either common or "fundamental" and worth dedicated primitives if they help with performance:

• + (concatenation)
• len(b)
• b[n] (indexing)
• ==, != (python/mypy#10928)
• <, <=, etc.
• b[:n] etc. (slicing) (python/mypy#10966)
• s.encode(<literal>) (for utf8, ascii and latin1)
• `s.encode(

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

(exp (log (make-polar 1.7976931348623153e+308 -1.797693134862315e+308)))

produces -8.648665413126592e+306-1.7956115019091953e+308i in Racket but -inf.0-inf.0i after Typed Racket optimization. Optimized code is:

(let-values (((g3)                                        
                    (#%app                                      
                     log