Skip to content

launchIDE requires the project to compile #4469

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Blaisorblade opened this issue May 6, 2018 · 4 comments
Closed

launchIDE requires the project to compile #4469

Blaisorblade opened this issue May 6, 2018 · 4 comments

Comments

@Blaisorblade
Copy link
Contributor

I like to use an IDE to fix my type errors. This also requires the project to fully compile, not just to compile with the presentation compiler, so it will fail even for code that passes the presentation compiler and/or can produce Tasty (but fails later).

Since I see why having some compiled output helps, I'm not sure what the architecture should be here.

@smarter
Copy link
Member

smarter commented May 6, 2018

Compiling before starting the IDE hasn't been strictly necessary for a couple of months now (if a classfile is older than a corresponding source file, the source file will be typechecked), but it's still useful to have classfiles for everything for performance in the IDE. It should be possible to make launchIDE compile the project, and then start the IDE even if it doesn't compile.

@Blaisorblade
Copy link
Contributor Author

But should the IDE use classfiles or tasty, long term? The latter could give superior results, but I don't know how it relates to the current roadmap.

@smarter
Copy link
Member

smarter commented May 6, 2018

When I say classfiles I mean the tasty part of classfiles.

@nicolasstucki
Copy link
Contributor

This is a duplicate of #3114

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants