| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Support visibility control and default to `internal`. (#3380) | Yong He | 2023-12-06 |
| | | | | | | | | | | | | | | | | | | | | * Support visibility control and default to `internal`. * Fix wip. * Fixes. * Fix. * Fix test. * Add legacy language detection and compatibility for existing code. * Add doc. --------- Co-authored-by: Yong He <yhe@nvidia.com> | ||
| * | Include imported code when generating reflection data | Tim Foley | 2017-06-26 |
| - The basic idea is simple: be sure to enumerate code in `__import`ed modules when generating reflection info - Note that we don't currently allow an entry point to appear in an imported module, so we only consider globlal-scope parameters - Although there isn't currently a real implementation of namespacing, I went ahead and ensured that parameters in imported modules are treated as distinct from parameters in the user's code, even if they have the same name. | |||
