[bugfix] Drop functionsOrdered argument from AbstractInternalModule constructor#384
[bugfix] Drop functionsOrdered argument from AbstractInternalModule constructor#384joewiz wants to merge 1 commit into
Conversation
…onstructor eXist-db/exist#6378 (PR eXist-db/exist#6384) removes the 3-arg `AbstractInternalModule(FunctionDef[], Map, boolean)` constructor. The 2-arg form is now the only path; the base class always sorts the function table and always binary-searches. This commit drops the now-removed third argument. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
[This response was co-authored with Claude Code. -Joe] Closing — obsoleted by #367's merge. That PR removed |
|
[This response was co-authored with Claude Code. -Joe] Status update: this PR is now optional cleanup rather than required. Per @line-o's review on eXist-db/exist#6384, the 3-arg The PR is still worth merging when convenient — dropping the unused third argument removes the warning and is the conventional Java forward path — but it's no longer time-sensitive. Feel free to merge or defer. |
|
(Oops, obviously, that last comment was no longer relevant for this PR. Please disregard. Sorry for the noise.) |
Companion to eXist-db/exist#6384 (closes eXist-db/exist#6378). That PR removes the 3-arg
AbstractInternalModule(FunctionDef[], Map, boolean)constructor — the base class now always sorts the function table and always binary-searches, so the third argument has no remaining purpose. The flag was the root cause of #6376 (silent function-lookup failure when the FunctionDef[] wasn't sorted).This one-line change drops the now-removed third argument so the build continues to compile once eXist#6384 merges.
No behavior change at the module level — the previous
falsevalue was either redundant (true → array was sorted anyway via the static sort idiom, or sort+binary was unnecessary at this module's scale) or implicit in the new always-sort behavior (false → linear scan and always-binary-search are equivalent for correctness; both find the function). The function lookup contract is unchanged.[This response was co-authored with Claude Code. -Joe]