Fix #5645 - SWIG 4.4.0 breaks Python and Ruby bindings for methods taking std::vector<T> where T is only forward-declared in the defining .i module5645 swig

[jmarrec]

Pull request overview

• Fix the item 3 of SWIG 4.4.0 breaks Python and Ruby bindings for methods taking std::vector<T> where T is only forward-declared in the defining .i module #5645

Ideally a newer SWIG version will fix it, but for now the workaround is to do the same as we do for C#: ignore, and reimplement later.

• std::vector<T> parameter/return type breaks across %import'd modules when T is only forward-declared in one of them swig/swig#3553
  • PR: Fix #3553 - Fix cross-module std::vector<T> mangled-name mismatch swig/swig#3554

With this, OpenStudio-resources tests shadowcalculation.{py,rb}, shadingcontrol_singlezone.{py,rb} now work.

Pull Request Author

• Model API Changes / Additions
• Any new or modified fields have been implemented in the EnergyPlus ForwardTranslator (and ReverseTranslator as appropriate)
• Model API methods are tested (in src/model/test)
• EnergyPlus ForwardTranslator Tests (in src/energyplus/Test)
• If a new object or method, added a test in NREL/OpenStudio-resources: Add Link
• If needed, added VersionTranslation rules for the objects (src/osversion/VersionTranslator.cpp)
• Verified that C# bindings built fine on Windows, partial classes used as needed, etc.
• All new and existing tests passes
• If methods have been deprecated, update rest of code to use the new methods

Labels:

• If change to an IDD file, add the label IDDChange
• If breaking existing API, add the label APIChange
• If deemed ready, add label Pull Request - Ready for CI so that CI builds your PR

Review Checklist

This will not be exhaustively relevant to every PR.

• Perform a Code Review on GitHub
• Code Style, strip trailing whitespace, etc.
• All related changes have been implemented: model changes, model tests, FT changes, FT tests, VersionTranslation, OS App
• Labeling is ok
• If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
• If feature, test running new feature, try creative ways to break it
• CI status: all green or justified

[github-actions]

🧪 Test Results Dashboard

Summary

Metric	Value
Total Tests	0
Passed	0
Failed	0
Errors	0
Skipped	0
Success Rate	0.0%
Generated	2026-08-31 14:01:35 UTC

❌ Significant Test Failures

📊 Test Run Information

Run	XML File	Status
-	No XML files found	❌ Missing