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
So the idea is to use @noscript to control things that should be hidden from script, this is obvious I think, but how can we assert such control over 3rd party libs?
Thing is, the metatable is created first time a value is pushed... but we want to influence the creation of the metatable for some particular 3rd party type.
We'll need some sort of pre-registration function I think which can pre-create the metatable, where we can supply a type, and also a member shadow list or something.
Thoughts? (I just opened this issue to keep thoughts/plans in a public place)
The text was updated successfully, but these errors were encountered:
I think I intended registerType to do this job, but I got side-tracked by working on pushing the static interface. Maybe the same function can be overloaded to take a filter function which spits out a bool given a fully qualified identifier? It can all be done at compile-time.
The intention is to add support for pushing entire modules automatically, so this is relevant for that too.
So the idea is to use @noscript to control things that should be hidden from script, this is obvious I think, but how can we assert such control over 3rd party libs?
Thing is, the metatable is created first time a value is pushed... but we want to influence the creation of the metatable for some particular 3rd party type.
We'll need some sort of pre-registration function I think which can pre-create the metatable, where we can supply a type, and also a member shadow list or something.
Thoughts? (I just opened this issue to keep thoughts/plans in a public place)
The text was updated successfully, but these errors were encountered: