You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 10, 2022. It is now read-only.
Using the single crate mechanism is not easy to setup because:
of the specific targets dependencies
it doesn't work very well with cargo. Sometimes cargo build the lib.rs even if it is not asked for it
It's also annoying for autocompletion and cargo check command as they don't work because of the limitation of the target on lib.rs.
For all those reason it is best to actually force the user to separate the run crate from the app crate. Making the first argument of the proc macro required is also a good thing because it's easy to forget that it exists (it's the name of the frontend crate in the workspace).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Using the single crate mechanism is not easy to setup because:
cargo check
command as they don't work because of the limitation of the target onlib.rs
.For all those reason it is best to actually force the user to separate the
run
crate from theapp
crate. Making the first argument of the proc macro required is also a good thing because it's easy to forget that it exists (it's the name of the frontend crate in the workspace).The text was updated successfully, but these errors were encountered: