typing

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.

Currently all responses return 200 (unless there is a server error, in which case 500).

It would be best to have specific codes for different types of errors to differentiate between them.

Example:

400 - Bad request

etc.

Problem

We could improve the readability / experience reading through the library source code if there were module level docstrings.

Suggested solution

All python modules should include a docstring explaining

Ideally there should be a way to install on at least some machines without cargo. This will need an installation script to install the language files in lieu of build.rs.

Some alternative installation methods which would be good to include are:

• sh installation script w/ prebuilt binaries
• AUR package

For prebuilt binaries, it would be ideal to setup GitHub workflows or similar so

An example of caching in CI for a rust project: https://github.com/mobusoperandi/michie/blob/4d9584c920223e9891b59de1a013f2bf7c886dcb/.github/workflows/ci.yml#L15-L25

Note that toipe does not use cargo-run-bin, so some of that can be removed.