fix: lints to guest programs

[rkdud007]

target to resolve #1125
q. cannot find **/test/programs so had with examples/*

[jonathanpwang]

By **/test/programs I was referring to https://github.com/openvm-org/openvm/tree/main/extensions/algebra/tests/programs (and analogous ones for other extensions)

[rkdud007]

@jonathanpwang so linting **/test/programs and examples/* and extensions/*/tests/* these 3? or should I remove examples/* now

[jonathanpwang]

I think we can keep examples/*. So that in addition to:

find . -type d -name "programs"

./crates/toolchain/tests/programs
./extensions/pairing/tests/programs
./extensions/bigint/tests/programs
./extensions/keccak256/tests/programs
./extensions/rv32im/tests/programs
./extensions/ecc/tests/programs
./extensions/algebra/tests/programs
./benchmarks/programs

[jonathanpwang]

LGTM after adding the other **/programs directories

[rkdud007]

Personally imo instead of allow clippy for functions like mult, have guest util crate and ppl can import it sounds nicer - also if then as its abstracted under other crate can just use iterator for have perf - but mb not scope of this PR : )

[jonathanpwang]

Some CI tests are failing; you may need to merge/rebase main, and also an issue with std

[jonathanpwang]

Can you merge main?

[rkdud007]

umm issue was prob not from main merge ( also did one) it from extensions/pairing/tests/programs/*/ which by removed unused variable lead to err on integration test, I backed up imported variables and just #![allow(unused_imports)] my this guess correct prob work now

[jonathanpwang]

I see, I think because pairing test require feature bn254 or bls12_381. Let's hope it works now.

[jonathanpwang]

Personally imo instead of allow clippy for functions like mult, have guest util crate and ppl can import it sounds nicer - also if then as its abstracted under other crate can just use iterator for have perf - but mb not scope of this PR : )

Yea I agree this is best practice. In this case the functions in those examples were purely one-time tests, so we don't really expect to re-use and they're not perf critical.