Tim Hutt

Ah ok, maybe a comment in the example is sufficient for now.

Like ``` // This is re-exported as `crossbeam::scope`. Unless you // are using crossbeam_utils directly you should `use crossbeam::scope` // here instead. use crossbeam_utils::thread::scope; ... scope(... ```

Seems like this never went anywhere? Bit of a shame. Makes it way harder to learn for beginners.

I have added typings to most of `Mobject.py`. One tricky issue is `Sequence[float]` vs `np.ndarray`. They're not compatible types in general and it's not clear where you need to use...

Here it is: #2129 I put `TODO(types)` comments where there are remaining type issues, as identified by Pyright (only at the first instance for each kind of issue).

Here's one: [remote_control_-_Top_Copper.gbr.zip](https://github.com/monostable/awesome-electronics/files/749911/remote_control_-_Top_Copper.gbr.zip) Apparently the issue arises because DesignsparkPCB doesn't close polygons, and the behaviour for that is undefined in the gerber spec. But every manufacturer I've sent them to...

It works for me in the `Command Prompt` and Powershell. Windows 10.0.19042.928. 

This is kind of infuriating. What is involved in fixing it? Can I just make the `4` configurable [here](https://github.com/rust-analyzer/rust-analyzer/blob/e535489f03901ab94a89dd2de67f35714f0c3cfc/crates/syntax/src/ast/edit.rs#L578) and [here](https://github.com/rust-analyzer/rust-analyzer/blob/e535489f03901ab94a89dd2de67f35714f0c3cfc/crates/syntax/src/ast/edit.rs#L605) and add some kind of flag to tell it...

I already linked where it is hardcoded. See my comment above and @matklad 's reply - which to be honest I didn't really understand.

Is anybody working on this?