Skip to content

Namespacing of functions / aliasing imports #433

Description

@rkalis

Right now, imports are full-file flat imports (import "./lib.cash"). That works fine on a small scale, but when people are publishing libraries to npm, it becomes harder to manage potential name collisions. That is why we want to allow aliasing/namespacing of imports, and also potentially only importing specific functions/globals from a file. See below:

// Alias imports + import specific functionsimport{func1,func2asfuncX}from"./lib.cash";// Alias the entire import (accessed as Lib.func1(...)import*asLibfrom"./lib.cash"// Alternative syntaximport"./lib.cash"asLib;

(created from #369)

Metadata

Metadata

Assignees

No one assigned

    Labels

    cashc-compilerRelates to the cashc compiler

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions