Skip to content
Rust SDK CI

Rust SDK CI #259

Sign in to view logs

Rust SDK CI

Rust SDK CI #259

Triggered via schedule November 30, 2024 01:12
@z4kn4feinz4kn4fein
⁠ 751fea8
main
Status Failure
Total duration 1m 1s
Artifacts –

ci.yml

on: schedule
test
52s
test
format
17s
format
clippy
36s
clippy
publish-dry-run
0s
publish-dry-run
Fit to window
Zoom out
Zoom in

Annotations

10 errors
clippy: src/builder.rs#L33
it is more idiomatic to use `Option<&T>` instead of `&Option<T>`
clippy: src/builder.rs#L53
it is more idiomatic to use `Option<&T>` instead of `&Option<T>`
clippy: src/builder.rs#L57
it is more idiomatic to use `Option<&T>` instead of `&Option<T>`
clippy: src/client.rs#L520
it is more idiomatic to use `Option<&T>` instead of `&Option<T>`
clippy: src/eval/evaluator.rs#L103
it is more idiomatic to use `Option<&T>` instead of `&Option<T>`
clippy: src/eval/evaluator.rs#L143
it is more idiomatic to use `Option<&T>` instead of `&Option<T>`
clippy: src/eval/evaluator.rs#L303
it is more idiomatic to use `Option<&T>` instead of `&Option<T>`
clippy: src/eval/evaluator.rs#L322
it is more idiomatic to use `Option<&T>` instead of `&Option<T>`
clippy: src/eval/evaluator.rs#L380
it is more idiomatic to use `Option<&T>` instead of `&Option<T>`
clippy: src/eval/evaluator.rs#L468
it is more idiomatic to use `Option<&T>` instead of `&Option<T>`