When looking at typical texvcjs parse trees one sees quite a few curly elements, those always have a single array element that might be empty. I think one could replace curly with an array-element and add a property, e.g., hasCurlies, to texArray. While this would add an if statement to the rendering call of texarray, I guess it would overall improve performance, reduce the size of the codebase and increase the readability of the codebase.
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| Fix call to isCurly of null | Physikerwelt | mediawiki/extensions/Math | master | +1 -1 | |
| Remove curly | Physikerwelt | mediawiki/extensions/Math | master | +100 -154 |
Event Timeline
Comment Actions
I think when working in debugger with the codebase (speaking for TexVC-PHP which is similar atm) then it is fine to have the curly element when viewing the parsetrees. TexArray with a property could obfuscate things in this matter.
Comment Actions
Change 1004311 had a related patch set uploaded (by Physikerwelt; author: Physikerwelt):
[mediawiki/extensions/Math@master] Remove curly (WIP)
Comment Actions
Change #1004311 merged by jenkins-bot:
[mediawiki/extensions/Math@master] Remove curly
Comment Actions
Change #1019059 had a related patch set uploaded (by Physikerwelt; author: Physikerwelt):
[mediawiki/extensions/Math@master] Fix call to isCurly of null
Comment Actions
Change #1019059 merged by jenkins-bot:
[mediawiki/extensions/Math@master] Fix call to isCurly of null