plugin: using coverpkg when testing results in plugin version mismatch #23410
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
The text was updated successfully, but these errors were encountered:
The test case was created by @jdef in 2018. It was done professionally from community. I gave him a thumb up for that.
But there is no response from the Golang team for 2 years! People pretend the problem doesn't exist because it may be not in line with the interest of their company. Is this an open source project still driven by a community or a private one dedicated for ONE commercial company?
I don't see the intention of generating the hash for Golang plugin at link time and verifying the hash at run time when loading it from the main process. If you want to prevent dependency version mismatch between the main process and the plugin, you should leave it to the programmers to decide. Not Go compiler. Because Go compiler has no idea about the semantic nor the contract of the dependencies. Instead of solving any practical problem, the hash itself has been a trouble maker for years.
The plugin in Go runtime is being implemented without any proper documentation. There is NO Go runtime specification that I can find online nor any open discussion of what plugin should be expected to behave. One guy from Golang team patch it until he thinks it is necessary. Then the behavior changes all in sudden. This is not acceptable for any programming language.
In addition, missing the unload plugin is another problem I want to chime in. I have never seen a program invoke
Please start to write a specification of Golang runtime or at least write a plugin specification. This development style by far handicaps Golang to be a mature language.