Project structure

[volsa]

Tracking issue for cargo workspaces, which we've already discussed internally. As a starting point something like the following seems fine?

• [x] plc_ast (https://github.com/PLC-lang/rusty/pull/889)
• [ ] plc_parser (includes the lexer)
• [ ] plc_resolver
• [x] plc_diagnostics (https://github.com/PLC-lang/rusty/pull/923)
• [ ] plc_index
• [ ] plc_validator
• [ ] plc_codegen
• [ ] plc_linker
• [x] rusty-standardfunctions (https://github.com/PLC-lang/rusty/pull/836)

This will bloat up the repository itself, so maybe we can pack these workspaces into a crates folder, such that the current structure of the project looks like:

book/
crates/
examples/
scripts/
README.md
...

Feedback welcome :)

Edit: It would be cool to check how the build times have changed, once all listed workspaces have been implemented.

[ghaith]

the repo is called rusty, so can drop the name from the subsequent folders maybe? I like the crates idea, and the top level would initially include things that have not been moved yet. Eventually it would be empty

[ghaith]

One more thing, the first workspace element is the Standard functions i guess :) there is an issue for that.

[volsa]

the repo is called rusty, so can drop the name from the subsequent folders maybe?

I think the naming prefix is the de facto standard, i.e. many popular projects use them; see

• https://github.com/rust-lang/rust/tree/master/compiler
• https://github.com/tauri-apps/tauri/tree/dev/core
• https://github.com/alacritty/alacritty
• https://github.com/helix-editor/helix

One more thing, the first workspace element is the Standard functions i guess :) there is an issue for that.

Thanks, totally forgot them. This should be the corresponding issue https://github.com/PLC-lang/StandardFunctions/issues/80