Skip to content
This repository has been archived by the owner on Jan 25, 2024. It is now read-only.

Investigate use of Pyre #371

Closed
trickeydan opened this issue Aug 7, 2019 · 4 comments
Closed

Investigate use of Pyre #371

trickeydan opened this issue Aug 7, 2019 · 4 comments
Assignees
Labels
enhancement New feature or request research This issue is being investigated. testing Test coverage. typing A incorrect or loose type that needs correcting. wontfix This will not be worked on
Milestone

Comments

@trickeydan
Copy link
Contributor

Kajetan has rightly pointed out that mypy is pretty awful.

Let us be enlighted by Ocaml

@trickeydan trickeydan added this to the 1.0.0 milestone Aug 7, 2019
@trickeydan trickeydan added enhancement New feature or request research This issue is being investigated. typing A incorrect or loose type that needs correcting. testing Test coverage. labels Aug 7, 2019
@trickeydan
Copy link
Contributor Author

pyre --source-directory j5 --verbose check
 ƛ Setting up a `.pyre_configuration` with `pyre init` may reduce overhead.
 ƛ Processed 30 of 57 sources [676.6s]

It's been stuck like this eating 100% of my CPU for 10 minutes.

@trickeydan
Copy link
Contributor Author

I've tried this again with the same result.

I'm going to call this a won't fix.

@trickeydan trickeydan added the wontfix This will not be worked on label Oct 19, 2019
@kierdavis
Copy link
Contributor

I get different output, but it still sits there pegging 100% CPU for multiple minutes.

Even if it does eventually finish, I'd deem this a major workflow breaker.

@trickeydan
Copy link
Contributor Author

I'm up for reopening this issue in, say 6 months, to see if it starts working.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request research This issue is being investigated. testing Test coverage. typing A incorrect or loose type that needs correcting. wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants