Skip to content
This repository has been archived by the owner on Aug 10, 2022. It is now read-only.

Make external crate "run" mandatory #60

Open
cecton opened this issue May 7, 2021 · 0 comments
Open

Make external crate "run" mandatory #60

cecton opened this issue May 7, 2021 · 0 comments

Comments

@cecton
Copy link
Member

cecton commented May 7, 2021

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).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant