Le Wed, 02 Oct 2013, David MENTRÉ a écrit :

> Hello,
> 
> 2013-10-02 19:06, Gabriel Scherer:
> >I think the most advanced project regarding IDE integration nowadays is
> >Merlin ( https://github.com/def-lkb/merlin ), which gives direct
> >feedback on syntax and typing errors. It doesn't have any knowledge of
> >unit tests or coverage checking, but it would probably be the right tool
> >to start with to integrate such a feature.
> 
> Thanks for the pointer.
> 
> >Note that there has been a bit of back-and-forth on the instant feedback
> >feature. Previous iterations were deemed a bit too visually invasive,
> >and some people don't like to risk being interrupted by their IDE while
> >they think about their code. I think it's always better to have the
> >feature available, but there is clearly some tuning to have, and
> >potential for overdoing it.
> 
> I've only seen demos and never used this feature a lot. You probably
> right that such a feature should be correctly tuned.
> 
> >The other project that jumps to mind is the Why3 IDE (
> >http://why3.lri.fr/ ). It seems they're not hype enough to have video
> >stuff available, but from what I remember the GUI does a pretty good job
> >of giving feedback on how external provers run, and pieces of code that
> >were previously verified and aren't anymore.
> 
> I've used Why3 IDE on a regular basis. This IDE is far from what I
> am looking for because one needs to do explicit actions to launch
> the provers. And Why3 IDE is focused on VCs, not the original source
> code (event if the code is displayed). Ideally, one would edit a
> WhyML file in an editor and the proved VC would be displayed
> automatically, like in Dafny. In fact the purpose of an editor I'm
> looking for would be to hide as much as possible the machinery to
> generate VC, launch provers, etc., from the user (and the same for
> test, doc generation, etc.). After all, when we call a compiler, we
> don't really care if the compiler, assembler or linker are needed
> and the files exchanged between them.

I agree with Gabriel, something close to what merlin does for type
errors would probably be the best thing. If tests were launched every
time you hit "save", run in the background, and display a warning (the
same way merlin already does for compilation warnings), it would be a
tight feedback loop indeed.

There are some facilities for writing unit tests directly in source
code, at least in Batteries. That would keep everything in the same
editor page.

My 2 cents

-- 
Simon