Vincent Esche

The proposed API would be extensible as well: ## Possible differential future If at some point ascent was to get proper support for re-entrant, differential programs, then `AscentProgram` could be...

Hi @StarGazerM, thanks for the very insightful feedback! I don't currently have any use case for an incremental ascent and was mostly including it for completeness sake and since ascent...

> I agree, reproducing these settings in cargo-modules is not needed. One argument for at least providing generalized `--graph`/`--node`/`--edge` CLI options that I'd see is that you might want to...

Big +1 on this one: > Also have a use case for this like the above: big C++ dependency that Rust builds via build.rs, but only necessary if things get...

In our use-case we have a heavy C++ library dependency that we cannot pull in and link to as a pre-compiled binary artifact as we want to be in control...

> Personally, I'm unfortunately not a fan of this API. I find it very confusingly structured and documented, and it isn't clear to me that the flexibility a visitor offers...

> I'm not the `cargo_metadata` maintainer so the final call isn't mine to make. But as a user of `cargo_metadata`, I wouldn't switch from what I currently have to a...

The tests were already failing for the upstream commit prior to this PR's changes. Not sure what to do about them. 🤔

> I've renamed `TAURI_SRC_DIR` to `TAURI_FRONTEND_PATH` and `TAURI_APP_DIR` to `TAURI_APP_PATH` to be more clear on what path does the env var refer to, what do you think? app and src...

@lucasfernog just updated the tauri CLI and got this: ```plain $ cd ./web-app $ pnpm tauri dev thread '' panicked at crates/tauri-cli/src/helpers/app_paths.rs:117:5: Couldn't recognize the `TAURI_FRONTEND_PATH` folder as a Tauri...