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
{{ message }}
Repository navigation
Directives above @usage header only apply to first @usage #74
only the first usage will get @dict SomeDict and show up in the docs as SomeDict.Foo. The second usage will show up as x#Foo since it's not considered a dict function.
This can be worked around by placing all directives that should apply to all usages after an @all directive, or by making sure they come after each @usage directive, but it's unintuitive and can bury directives that you'd expect to see on the first line.
Opened #145 with a fix. Metadata present before the first header is now inherited by every usage; directives placed after a header remain specific to that variant.
The regressions cover dictionary naming across three usages, @public, and per-usage isolation. Two regressions fail on current upstream and all 12 tests/doctest modules pass with the fix. Hosted checks are tracked on the PR.
Activity
vinsymoyya commentedon Nov 12, 2026
Opened #145 with a fix. Metadata present before the first header is now inherited by every usage; directives placed after a header remain specific to that variant.
The regressions cover dictionary naming across three usages,
@public, and per-usage isolation. Two regressions fail on current upstream and all 12 tests/doctest modules pass with the fix. Hosted checks are tracked on the PR.