current-module / current-package

[amitu]

current-module.foo will resolve to the .foo defined in the module that is currently being "served". current-package will resolve to the top level index.ftd of the package.

Special variables:

$current-module.file-name, $main-package.FASTN-PACKAGE etc.

What if the module has already defined $current-module?

Option 1: The automatic variable $main-module will be shadowed by the definition.

Option 2: current-module is a language reserved keyword and can not be used as name. Biased towards this.

[amitu]

What if we introduce a type called current-module:

-- current-module m1: some-module-1
-- current-module m2: some-module-2

If m1 is referred during rendering of current page, current-module must implement some-module-1 and if m2 is referred current-module must implement some-module-2.

Both m1 and m2 can be accessed if current-module implements both some-module-1 and some-module-2.

[amitu]

-- current-module m1: 

-- integer x: 10

-- end: m1

This syntax should also be implemented for module:

-- module m:

-- integer x: 10

-- end: m

-- ftd.integer: $m.x

module needs to be explicitly assigned, current-module gets automatically assigned.