Conversation

But have the class gets stuck figuring out the interface and doesn't have enough time to work on that. So when I ask about their experiences and how they could make it easier (it's a proof automation class), many of the answers are complaining about holes and the interface
1
2
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
VSCode doesn't seem much better than emacs for Agda honestly. Students still found it confusing and had to learn weird emacs bindings
3
3
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Yeah the continuous editing in Lean is something I love so much! I love it how things live update as I do stuff, but maybe I’m just used to that from other languages… I generally use source control if I want to remember a past state.
2
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Yeah, having tactics be in the same language as the proof assistant *and* being a jump-to-defintion click away in an IDE is a massive win for learning and accessibility, at least for people like me. Can't remember if Isabelle had something similar as well.
2