4 ms·
Wait, so they don’t have test parity with git? How do they know that they, umm … did the actual thing they were trying to do?
by rao-v 7mo ago
Wait, so they don’t have test parity with git? How do they know that they, umm … did the actual thing they were trying to do?
- didgetmaster 7mo agoI have heard that you can speed up your favorite compression algorithm by 1000x, if you are not so concerned about what happens when you try to decompress it.
- magackame 7mo agoAlso gotta love the write-only disk as a hardware analogy. Insane write speeds and infinite capacity...
- delusional 7mo agoIt's just a lossy compression scheme.
- yevbar 7mo agoI ran the test suite specifically for git's CLI as that was the target I wanted to build towards (Anthropic's C compiler failed to make an operating system since that was never in their original prompts/goals) The way it gets organized is there are "scripts" which encompass different commands (status, diff, commit, etc) however each of these scripts themselves contain several hundred distinct assertions covering flags and arguments. The test suite was my way of validating I not only had a feature implemented but also "valid" by git's standards
- djoldman 7mo agoThis is the same as all the folks asking for and hawking quantized models. It doesn't matter if the parent model is GPT GOD mode mythos opus 100x Ultra. What matters is the performance of the quantized model.