libera/#sicl - IRC Chatlog
Search
3:05:07
Bike
nope, completely different personal project. how would conspack help with a linter? i guess you could write out a report densely...
3:05:53
beach
Yeah, they didn't seem related, but I don't think you described that other project, so I was wondering.
3:07:30
Bike
oh, no. i'm working on a video game in my spare time and i want to use conspack to save the game state.
3:07:54
Bike
figure i should work on something that is an actual user facing application for once in my life
3:19:05
Bike
if you have ideas for what i should put in the linter i would be happy to hear them. that's probably the main thing i need right now, other than finishing the abstract interpreter
3:26:19
Bike
not yet. most of the reason i haven't done much on it is not having a solid idea of what people would want from a linter. i think basically stuff compilers don't do would be good, so interfunction analysis and conformance checks are on there
3:28:17
beach
You could have an option for catching LUV-page-13 things if you aim for style issues as well.
3:29:01
beach
Another style issue for recursive functions would be to make sure the base case is handled first.
3:29:30
Bike
style issues would probably have to be in there. i think that's what the existing linters mostly do, at least for lisp.
3:35:05
beach
I guess a COND or a CASE without a default clause in a context where values are needed is problematic as well, but then, it could be that such a form is the last one of a function, and no calls to the function uses the values, so then it is OK.
3:49:05
Bike
violations of loop clause order is a big one. wasn't xach using the sicl loop to catch problems with that implementations passed through? that's a big area a linter could help.
4:18:55
Bike
implementations are naturally not too motivated to find things that could hypothetically be a problem in some other implementation, so a linter could be good there