Help AI coding agents use Java Streams and Collectors well in new code, review, and cleanup without replacing one antipattern with another.
100
100%
Does it follow best practices?
Impact
100%
2.17xAverage score across 4 eval scenarios
Passed
No known issues
{
"context": "Main eval weighted natural implementation: non-overlapping Java 24 bounded remote-check scenario; measures bounded stream concurrency for blocking calls without reusing runtime favorite-products examples.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Creates coherent Java 24 artifact",
"description": "Creates DeliveryAppointments.java with the requested method, nested types, imports, and Java 24-compatible code.",
"max_score": 20
},
{
"name": "Preserves appointment behavior",
"description": "Returns only appointments whose token passes CalendarService.canSchedule and sorts the final returned appointments by Appointment::startsAt, then Appointment::token.",
"max_score": 40
},
{
"name": "Uses bounded Gatherers.mapConcurrent",
"description": "Uses Gatherers.mapConcurrent with an explicit max concurrency no greater than 8 to perform the blocking CalendarService.canSchedule calls inside the stream chain.",
"max_score": 180
},
{
"name": "Carries appointment with schedule result",
"description": "Keeps each Appointment associated with its schedule-check result using a non-null holder, then filters by the boolean result before mapping back to Appointment.",
"max_score": 80
},
{
"name": "Rejects weak concurrency choices",
"description": "Does not use parallelStream(), .parallel(), unbounded CompletableFuture fan-out, or shared mutable state for collecting remote check results.",
"max_score": 60
},
{
"name": "Keeps implementation focused",
"description": "Avoids unrelated caching, retries, dependencies, API redesign, or broad concurrency framework changes.",
"max_score": 20
}
]
}