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.
Gagan Devagiri built a pipeline similar to the Decisions API a few weeks ago using Parallel's web search and Jev for Pi, noting a preference for separating retrieval and judgment in coding workflows.
Funny timing -- Parallel just announced its Decisions API; I built a similar pipeline a few weeks ago at the application layer using Parallel's web search and Jev for Pi: https://github.com/GaganSD/pi-extensions/tree/main/pi-web-search… After using this, I prefer separating retrieval and judgment for coding and