# When working on a project (not a package, not intention of re-use), I started usin

**URL:** <https://discourse.julialang.org/t/when-working-on-a-project-not-a-package-not-intention-of-re-use-i-started-usin/54331>\
**Category:** General Usage\
**Created:** [January 31, 2021, 3:40pm UTC](https://discourse.julialang.org/t/when-working-on-a-project-not-a-package-not-intention-of-re-use-i-started-usin/54331 "2021-01-31T15:40:28Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pdeffebach](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pdeffebach/32/10320_2.png) [@pdeffebach](https://discourse.julialang.org/u/pdeffebach)\
**Post date:** [January 31, 2021, 4:28pm UTC](https://discourse.julialang.org/t/when-working-on-a-project-not-a-package-not-intention-of-re-use-i-started-usin/54331/2 "2021-01-31T16:28:21Z")

</div>

Update from slack:

1. If you want to enable precompilation of your functions, use a module. However as this is a project that is not designed for re-import into another body of work, this is not an added benefit of modules in this context.
2. You can use

```julia
for n in names(@ __MODULE__ ; all=true)
    if Base.isidentifier(n) && n ∉ (Symbol(@ __MODULE__ ), :eval, :include)
        @eval export $n
    end
end

```

at the end of your module to automatically export all Symbols.

However this has no added benefit that just working with `includet` doesn’t provide, at least for my use case.

So I think it is best to keep `includet` for now. My final concern is that I don’t know if `includet` is as feature rich as using Revise with a module.

If anyone has examples of edge cases in which using Revise with a module works but `includet` has some problems, I would appreciate hearing them.

---

_[View the full topic](https://discourse.julialang.org/t/when-working-on-a-project-not-a-package-not-intention-of-re-use-i-started-usin/54331)._