Showing that a novel mathematical approach was in your prompts shortly before the model “proposes” that approach to relative amateurs would be ideal, if only we had a case like that…
It’s possible that they didn’t train on it, and the approach was derived by the LLM.
What’s a problem is that they haven’t outright denied it. That could be caution and them doing their due diligence first, it could be that it was intentional and they didn’t expect to get caught, or it could be because they have no way of knowing themselves.
Once a model like Fable/Mythos is trained, that was used for this project, the inference costs are profitable. CapEx vs. OpEx. Every new Zig->Rust port of this caliber using Fable/Mythos costs the standard token price, it's not subsidized. The model already exists for the original CapEx, you can do 1,000 ports of this for standard token pricing.
Because they are an integral part of the solution generation.
By distilling, you are training a model via Reinforcement Learning (RL) to mimic the answer of a bigger model. To do that, you need all the steps that contributed to generating an answer.
To give you a better idea, imagine teaching a student how to solve math problem:
1. You give it the problem and the answer only (no thinking trace)
2. You give it the problem, the intermediary steps and the answer (full transcript)
I think you can agree that the second method is more likely to give a well-informed student.
I would like to add that for what it's worth, I wouldn't mind slower compilation times if it means we get the type system as described. If it really does end up having a significant impact on performance, would you be open to making compile-time type-checking optional instead of scrapping the whole thing?