[diziet]

I love llm coding. I don't know what I am looking at here

https://github.com/malisper/pgrust/blob/main/Cargo.lock

What is happening.

No PRs? No Make files? I understand running tests and debugging is the workflow, but where do you log things? How do you orchestrate builds? Etc.

[nemothekid]

`Cargo.lock` is a lockfile machine generated by Cargo. It's similar to package-lock.json. In any case, its machine generated the old fashioned way.

[diziet]

I am fully aware what Cargo.lock is. What I am surprised at is how many dependencies there are.

[antonvs]

Like most modern languages, Rust has its own build system and package manager, Cargo. Everything you're referring to relates to that, and has nothing to do with LLM coding.

Edit: saw the clarification in another comment. But, in that case the essential point seems to be "I'm not familiar with something, therefore it's suspect."

[kaoD]

> I love llm coding. I don't know what I am looking at here

There might be some correlation here.

[diziet]

I am fully aware what Cargo.lock is. What I am surprised at is how many dependencies there are.

[kaoD]

Sorry, the wording confused me.

The project itself seems to be structued around 1.4k micro-crates[0] which I admit is a bit weird. Rust's compilation unit is the crate unlike C's per-file compilation unit, so if this was a 1:1 AI-assisted translation from the original Postgres source this might be an artifact of the translation.

[0] https://github.com/malisper/pgrust/blob/main/Cargo.toml

[malisper]

This is correct. We first used c2rust to translate the C into unsafe Rust. The generated Rust code had one crate per C compilation unit. We then took the unsafe unidiomatic Rust and one crate at a time converted it to safe Rust.

[r_lee]

it's like node_modules but cooler