Unlike other popular Cargo commands, cargo-atcoder currently assumes that CWD equals $CARGO_MANIFEST_DIR. We will be able to run cargo-atcoder everywhere under the workspace directory.
To support --manifest-path and -p|--package.
Building dependencies takes long time in general. Even proconio takes about 30 seconds with the derive feature.
Warming up release build for `abc152`...
Compiling proc-macro2 v0.4.30
Compiling unicode-xid v0.1.0
Compiling syn v0.15.44
Compiling lazy_static v1.4.0
Compiling quote v0.6.13
Compiling proconio-derive v0.1.6
Compiling proconio v0.3.6
Compiling abc152 v0.1.0 (/home/ryo/src/local/abc152)
warning: unused variable: `n`
--> src/bin/b.rs:5:9
|
5 | n: usize,
| ^ help: consider prefixing with an underscore: `_n`
|
= note: `#[warn(unused_variables)]` on by default
Finished release [optimized] target(s) in 41.81s
I'd like to propose that we create a large workspace and add the packages to the workspace members. In this way, we can keep using one build cache with the same dependency graph.
(edit) Then we would have to put profile.release on the root manifest, and to rename bins uniquely.
To free from CWD.
Unlike other popular Cargo commands,
cargo-atcoder
currently assumes that CWD equals$CARGO_MANIFEST_DIR
. We will be able to runcargo-atcoder
everywhere under the workspace directory.To support
--manifest-path
and-p|--package
.Building dependencies takes long time in general. Even
proconio
takes about 30 seconds with thederive
feature.I'd like to propose that we create a large workspace and add the packages to the workspace members. In this way, we can keep using one build cache with the same dependency graph.
(edit) Then we would have to put
profile.release
on the root manifest, and to renamebin
s uniquely.Currently,
cargo-atcoder
does not work with such a workspace. Withcargo metadata
, we can usecargo-atcoder
on large workspaces.