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.

Sign up for GitHub

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

Jump to bottom

Does the analyzer actually analyze anything? #40

Closed
ErikSchierboom opened this issue Oct 31, 2023 · 4 comments
Closed

Does the analyzer actually analyze anything? #40

ErikSchierboom opened this issue Oct 31, 2023 · 4 comments
Assignees
@verdammelt

Comments

@ErikSchierboom
Copy link
Member

I've been looking at the analyzer code for a bit, and to my untrained eyes it looks like it doesn't really analyze anything yet. Is that correct? If it doesn't, I would suggest disabling the analyzer in the track config (https://github.com/exercism/common-lisp/blob/main/config.json#L9), as that will save us some resources.
@verdammelt
Copy link
Member

No it does not analyze. I wrote this code to give the "frame" to put the analyzer into. But then I have never gotten around to writing it :(

@ErikSchierboom
Copy link
Member Author

No worries. If you could be so kind to disable the analyzer then please :)

@verdammelt
Copy link
Member

I will do that tonight (Eastern US time)

verdammelt added a commit to exercism/common-lisp that referenced this issue Nov 1, 2023
@verdammelt
Turn off the analyzer as it still doesn't do anything.
8f71e1a 
(_cf._ exercism/common-lisp-analyzer#40)
@verdammelt verdammelt mentioned this issue Nov 1, 2023
Merged
@verdammelt
Copy link
Member

Turning off the analyzer on the track for now.

(cf. exercism/common-lisp#761)

verdammelt added a commit to exercism/common-lisp that referenced this issue Nov 1, 2023
@verdammelt
Turn off the analyzer as it still doesn't do anything. (#761)
e8ddbf7 
(_cf._ exercism/common-lisp-analyzer#40)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@verdammelt verdammelt

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ErikSchierboom @verdammelt