PhobosV3+ Fundamental Elements

[Richard (Rikki) Andrew Cattermole]

On 20/09/2026 6:46 AM, Gregor Mückl wrote:
> On Saturday, 19 September 2026 at 18:27:24 UTC, Richard (Rikki) Andrew 
> Cattermole wrote:
>> On 20/09/2026 6:04 AM, Gregor Mückl wrote:
>>> Also, another scenario that I believe is full of nasty surprises is 
>>> when two shared libraries get loaded dynamcially by a process at 
>>> runtime that are built with different version of Phobos. Even if the 
>>> file names don't collide, the symbol names will because they have to 
>>> be exported. If Phobos was linked statically into each shared library 
>>> with hidden symbol visiblity, those issues would go away.
>>
>> Unless you are doing something more advanced build setup wise, you 
>> would also be using different compilers and druntimes too. That is not 
>> meant to work.
> 
> The presence of a different version of a library in the same process can 
> be something that is completely out of the control of the affected 
> developer. I can give you a few examples of how this kind of stuff can 
> get really uncontrollable:

Yes I am aware.

You the developer working in this environment need to be aware of it and 
the default configuration for things like the eventloop or GC is not 
going to be appropriate. You need to make informed decisions and take 
the appropriate actions.