https://bugzilla.wikimedia.org/show_bug.cgi?id=47104
Martijn Hoekstra <martijnhoeks...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |martijnhoeks...@gmail.com
--- Comment #5 from Martijn Hoekstra <martijnhoeks...@gmail.com> ---
The copy-on-write suggestion sounds mighty scary if a module could modify
loadData tables, and the modified table would be exposed to *other* modules. I
think module writers want to be assured that when they loadData, the data is
guaranteed not to be changed. I find it hard to come up with a reasonable
scenario where a mutable loadData would be required, and it would create a
dependency between a first #invoke of a module to subsequent invokes. (that is,
to do something with the modified data on later #invokes you would need to know
that an earlier #invoke has actually modified the data.) While I can imagine
some situations where you would want to perform an expensive projection on
data, and performance requires you to do that transformation only once, it does
not sit quite right with me to create this kind of dependency between calls.
If this kind of thing were to be implemented, I'd personally rather see an
exposed _G.page, where page is either a table of settings for this module for
this page, or where page is a table of module names with stored values for the
module for the page (possibly with a metatable set to the running modules table
for syntactic sugerring, so one can call page.myValue rather than
page.thisModuleName.myValue)
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
