You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now signature ascription works well for individual modules. But there's no way to ascribe a signature to multiple modules (e.g. all modules in a package or subdirectory tree) such that they see (some of) each others details but those details are hidden from clients outside the package. This works in the theory, but there is a practical problem that there's no way to specify it right now.
Option 1: ascribe a signature to an entire subdirectory tree
Option 2: have a way of specifying that certain members are hidden outside a particular scope (but visible within that scope). This is really an abbreviation/convenience for doing option 1.
The text was updated successfully, but these errors were encountered:
Kind of! Wyvern's theory derives from that of Standard ML, so it supports hierarchical modules well. The question is, how do you make it work with separate files--without going to a hacky textual import approach?
Right now signature ascription works well for individual modules. But there's no way to ascribe a signature to multiple modules (e.g. all modules in a package or subdirectory tree) such that they see (some of) each others details but those details are hidden from clients outside the package. This works in the theory, but there is a practical problem that there's no way to specify it right now.
Option 1: ascribe a signature to an entire subdirectory tree
Option 2: have a way of specifying that certain members are hidden outside a particular scope (but visible within that scope). This is really an abbreviation/convenience for doing option 1.
The text was updated successfully, but these errors were encountered: