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
We've been thinking how to name a family of functions in reflection that work with objects (aka modules in compiler speak). A few examples: staticModule, reflectModule, ModuleSymbol etc.
There's a concern that module would be ambiguous because of the associations with packaging, OSGI and stuff. Hence we're looking into the alternative names we could use.
The text was updated successfully, but these errors were encountered:
@xeno-by said:
We cannot use Scala's natural terminology and go for "object" here (as in "reflectObject", "staticObject" or "ObjectSymbol"), because that'd be very ambiguous. Therefore we need to come up with a new concept anyways. And if we have to do that, let's go for something that's already in the spec and in the compiler. Following this line of thought we decided to keep "reflectModule".
We've been thinking how to name a family of functions in reflection that work with objects (aka modules in compiler speak). A few examples: staticModule, reflectModule, ModuleSymbol etc.
There's a concern that module would be ambiguous because of the associations with packaging, OSGI and stuff. Hence we're looking into the alternative names we could use.
The text was updated successfully, but these errors were encountered: