Writing C++ with Jev by picking valid next tokens
The author experimented with TypeSafe's Jev decision/classifier model for C++: at each step it was given only grammatically valid next tokens to pick from, avoiding free-form generation.
Ronald te Brake shares an experiment using Jev for semantic test ranking: with a +1,394/-39 diff, 852 test files assessed, only 17 selected to run, ~$0.41 Jev input cost, 98% fewer tests.
Experimenting with Jev for semantic test ranking in our test impact analysis. One diff of +1,394 / -39: 852 test files assessed 17 selected to run ~$0.41 Jev input cost That's 98% fewer proposed tests. I manually checked the selection, and these were the tests I would have