Skip to content
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

How to handle the test folder #74

Open
davidanthoff opened this issue Jan 13, 2020 · 0 comments
Open

How to handle the test folder #74

davidanthoff opened this issue Jan 13, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@davidanthoff
Copy link
Member

Maybe more an issue for LS actually, but I think in general we need to come up with a plan what we do about the test folder.

I think fundamentally we should think of the code in the test folder as running in a different environment than the rest of the code, namely in a synthetic environment that is the union of the normal + test environment. Maybe the way to handle this is in the LS have two symbol stores, one for the "normal" code, one for the "test" folder. Then also have two instances of symbol server, And have them just return a symbol store for both.

The env for the test folder doesn't really exist on disc, so we'll have to create that from a merge from the default and test stuff. I think we might be able to reuse the code from the test runner in Pkg.jl for that.

I'd say we can solve this whole problem once we have the load times under control, i.e. next version :)

@davidanthoff davidanthoff added the enhancement New feature or request label Jan 13, 2020
@davidanthoff davidanthoff added this to the Backlog milestone Jan 13, 2020
@davidanthoff davidanthoff removed this from the Backlog milestone Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant