NobiGo commented on PR #3905: URL: https://github.com/apache/calcite/pull/3905#issuecomment-2287906828
> This PR should not affect the behavior of Calcite in this respect, other than fixing the bug. I believe that the first function that typechecks (where libraries are probed in the order they are specified) will be the one used, but this is not documented as far as I can tell. > > This may actually be a problem for projects that use multiple libraries: as Calcite evolves and adds overloads to these functions, and there are lots of them, with different behaviors, software using Calcite that used to work may stop working. But this is not a problem that is new. Thanks for your reply. When loading multiple libraries with identical function names if we don't throw exceptions and can clearly determine which library's function is effective, then I think it's not a problem for us. I'm worried we won't be able to decide on which library's function is effective. I will create another issue to document it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
