When generating reference docs (e.g. via Paka 🦙) it can be very helpful to mark exports with the @category JSDoc tag which enables grouping them in a semantically more meaningful way.

Here are a few example packages which already added the @example JSDoc tag:

• graphql-ws
• [@antfu/utils](https://www.paka.dev/npm

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

# typed: true
extend T::Sig

x = T.let(nil, T.nilable(Integer))
T.reveal_type(NilClass.===(x))

T.reveal_type(NilClass.===(T.unsafe(nil))

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

Currently pgTyped CLI package is using minimist for CLI flag parsing. By design minimist is rather minimal and doesnt provide any advanced features.

To improve the current CLI experience we should switch to yargs.

Things we will get out of the box with yargs:

• Help command
• Env variable support
• Flag value validation
• Documented default values

It's easy to forget to support dict subclasses when adding primitives, so it would
be good to have test cases that override all dict methods (and check that the
overridden implementations are used) to make sure this works as expected.

Note that until mypyc supports some additional dunder methods, this can't be
fully implemented.

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