zu-java was never zero - #575
Merged
Merged
Conversation
The row said zero on all ten items, which was not an audit. It was a row nobody had filled in, and a scorecard with a placeholder in it is worse than one with a gap, because the placeholder reads like a measurement. Audited, zu-java held two of them already. reference, because the javadoc is generated and published with the release rather than written by hand beside it, and CI builds it on every push so it cannot rot quietly. idiom, because the API is records, a sealed Value, AutoCloseable on every handle, Stream<Row> for iteration, text blocks in the examples and unchecked exceptions with a retryable field rather than a checked one on every signature. conditions is the third and it landed today, tamnd/zu-java#11. The code, the place and the doc URL are asserted on every failure that has them and asserted absent on the failures that do not, which is the part the old test could not do. 35 of 90. quickstart, misuse, leaks, install and stability are the apparatus still to build, and api-map and perf are reports.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The zu-java row said zero on all ten practice items. That was not an audit, it was a row nobody had filled in, and a placeholder is worse than a gap because it reads like a measurement.
Audited, zu-java already held two:
reference, because the javadoc is generated and published with the release rather than written by hand beside it, and CI builds it on every push so it cannot rot quietlyidiom, because the API is records, a sealedValue,AutoCloseableon every handle,Stream<Row>for iteration, text blocks in the examples, and unchecked exceptions with aretryable()field rather than a checked exception on every signatureconditionsis the third and it landed today as tamnd/zu-java#11. The code, the place and the doc URL are asserted on every failure that has them and asserted absent on the failures that do not. The old test usedifPresent, which passes when the field is missing, so the one outcome worth failing for was the one it let through.That is 35 of 90. What is left is
quickstart,misuse,leaks,installandstability, which are apparatus the repository has to grow, andapi-mapandperf, which are reports the release collects.zu-c is the other row still at zero and it is next after this. It is a different shape of audit, because the developer kit owes no api-map: the C names are
zu.handzu.his generated in the engine, which the table already says.Regenerated with
cargo run -q -p xtask -- clientson a server.