I’m new to Julia (2 weeks of exp). I would like to port and extend existing project from C++/python to julia. I’m having big difficulties in structuring my project. The project will contain roughly 50-100 files/modules, some modules will depend on other modules in the project. Coming from C++/python…

Majority of packages in julia implement the monolith pattern (#4) which I strongly object. Files should be self contained and testable. I’ve used many languages over 20 years of my professional career and this is the first time I don’t get it.

So, answering more specifically: I would check how many modules in your package can be translated into independent packages with a well defined functionality. That turns out to be very useful later, sometimes (happened to me) a subpackage ends up being more useful to the community (and to you) than …

I have a 100% success rate for functions that are defined inside my own module/project. It is true that it is not the case for navigation inside external packages. Usually I can click/jump into the source code on function from an external package but then I can’t continue to navigate further. What…

[image] LaurentPlagne: What I often do when I need to make a deep inspection of an external package is to install it’s repo and develop inside this package for a while This is precisely what I do as well (even though ideally it would be readable from the public repo alone…), and I still have …

[image] lmiq: This is a noble objective. But you won’t get that with Julia easily. (and ps: I do like how this works in Python). But it doesn’t have to be that way, option #1 is almost there. This seriously hurts adoption of Julia.

I don’t have much recent experience with largish Julia projects. But I am working on one now. At the moment, it has only one level of modules. Modules are more or less namespaces in Julia. Structs tend be be lighter weight than Python or C++ classes. Perhaps more like C structs. So even people who l…

I am glad to know this now, but I still feel strongly that such tricks (and these really are “tricks”) should not be necessary for something so fundamental as to discover “where is this code defined.” Especially given that not everyone wants to use VSCode.

[image] MacKa: But it doesn’t have to be that way, option #1 is almost there. This seriously hurts adoption of Julia Unfortunately :sweat_smile: this is not one of the major Julia pain points pushing people appart. Paraphrasing Tamas Papp, Julia is not an easy language. It is based on a diff…

I agree. @ffevotte explained to me a while ago how to place a main function inside the module sources during the development of a given package (leaving the launching scripts for later use). This technique should be better known. P.S. It is not only for vscode users (it is related to LSP).

How to structure project in julia

New to Julia

LaurentPlagne May 26, 2023, 8:31pm 26

This link may help to improve you navigation issues
LSP "Missing reference" woes - #11 by ffevotte

Topic		Replies	Views
Proper way of organizing code into subpackages New to Julia packages , code-organization	48	8388	August 24, 2022
[ANN] PatModules.jl: a better module system for Julia Package Announcements code-organization	70	9982	January 4, 2021
Organization of multiple modules in same package General Usage packages , modules , code-organization	18	5489	May 4, 2021
Implicitly loaded modules in the future? Internals & Design question , module , code-organization	281	17062	May 4, 2022
Organizing modules. Is it OK to organize a project using several modules in Julia? New to Julia	18	3546	February 13, 2020

How to structure project in julia

Related topics