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
This seems to work as expected. include A makes all features in A available in the parent namespace. A private macro is still visible from the same namespace, so it makes sense that you can call it after include A.
Note that the visibility of test does not change. Calling it from a different namespace is still prohibited.
moduleAprivatemacrotest(t)
{%puts"HI #{t}"%}
endendmoduleBincludeA
test(2)
endB.test(3) # Error: private macro 'test' called for B
Issue:
Using
include
with amodule
that has aprivate macro
exposes themacro
publiclyCode:
throws an
Error: private macro 'test' called for A
Produces:
What it should do:
Throw an
Error: private macro 'test' called for A
The text was updated successfully, but these errors were encountered: