-
Modules should be organized by nesting directories.
Definitions from one module should have straight accessibility from other module's parts.
e.g: examine the hierarchy:
```
app1
- frontend
…
-
Related to #5, #6
The next logical step is to have a clear, statically defined way to reason about the exports of a namespace as well as its imports. Clojure exports everything by default, which is …
-
- Statically analysable (so the equivalent of `import A from B` fails if `B` doesn't export a symbol `A`).
- Dead code elimination
Syntax ideas:
``` clojure
; named imports
(import `lib.peach` [a, b…
joews updated
7 years ago
-
The existing hack is a hacky hack which is actually _worse_ than `#include`.
I have two possible implementations in mind. One is akin to a mix of Haskell’s and Perl’s module systems. Important exampl…
-
Today I found really weird issue - I watched some code in `erlang.erl` and looks like system updated its access time, sync reloaded it and I found apply function going to infinitive loop on each call…
-
### Description of the new feature / enhancement
Hello,
I have been following along with the development of the PS Module and I can now see that it's working for PS 7 and PS5.1 however it does n…
-
I dare not even count the amount of times I've seen someone take the time to craft a wonderful message, explaining how to solve some issue, or approach some problem. In some cases, these messages can …
-
We need to go over all our modules and properly convert modules that are essential to system modules.
To do this is in THEORY very simple, simply change koinstall to kodistinstall in the Conscript.…
-
> Failed to transform core-for-system-modules.jar to match attributes {artifactType=_internal_android_jdk_image, org.gradle.libraryelements=jar, org.gradle.usage=java-runtime}.
> Execution fail…
-
I imagine something like:
```
# frob.koko
[ module
frob { @do-some-frobbing }
tweak { @tweak-it %1 }
gizmo xyz ]
```
```
:: [ use frob.koko ] , [ @tweak [ @frob @gizmo ] ]
```
But one c…