Thanks for sharing this sir! This is indeed a more scalable design than commit0 to evaluate the ability of models to generate libraries from scratch and will allow scaling to training data better than commit0. But I feel commit0 is more aligned with how real-world developers would want to do library generation (write the software specification + code skeleton and ask the model to fill it for you)? We won't have a binary to start with in a real-world use-case else that problem is already solved. Would love to know your thoughts on the best interface for library generation!
Though one interesting use-case if this is solved would be to reverse-engineer proprietary programs like nvcc 😅