Loader requires expected API endpoints to be present with the expected signature, otherwise it fails to load the DLL. This is desired for the public API, but it has also been mistakenly applied to the private/internal API. This means we are not free to remove or modify these functions.
Compatibility audit found that a recent change slated for 2.6.0 have changed an endpoint. The change causes the Loader to fail to find one of its required endpoints due to signature mismatch. The change needs to be altered such that it accomplishes its goal without modifying the signature of the private endpoint.
Furthermore, Loader should be modified so that missing or misaligned private endpoints do not cause a failure condition.
Loader requires expected API endpoints to be present with the expected signature, otherwise it fails to load the DLL. This is desired for the public API, but it has also been mistakenly applied to the private/internal API. This means we are not free to remove or modify these functions.
Compatibility audit found that a recent change slated for 2.6.0 have changed an endpoint. The change causes the Loader to fail to find one of its required endpoints due to signature mismatch. The change needs to be altered such that it accomplishes its goal without modifying the signature of the private endpoint.
Furthermore, Loader should be modified so that missing or misaligned private endpoints do not cause a failure condition.