Re: Simple example on interfaces

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2021-01-26 21:04, Shark8 wrote:
> On Tuesday, January 26, 2021 at 12:44:45 PM UTC-7, Dmitry A. Kazakov wrote:
>> Instantiation errors nobody can really predict. On top of that is
>> uncontrollable name space pollution.
> I submitted an AI that solves a lot of the pollution:
> http://www.ada-auth.org/cgi-bin/cvsweb.cgi/ai12s/ai12-0268-1.txt?rev=1.3&raw=N

Well, it would have only limited use.

The case you present is rather solved by using child generics as they 
"inherit" parameters. So

    generic
    package Generic_Swap.Generic_Stack is

And here we come to the real-world problem. Generic packages and their 
formal parameters are organized in a directed acyclic graph like:

     A   D
    / \ /|
   B   C |
    \ /  |
     E   |
      \ /
       F

rather than a tree. You want to instantiate the whole graph in a single 
shot. You do not want to manually specify constraints on generic formal 
parameters when some of them travel by several paths as D into F.

BTW, observe similarity with diamond/rhombus MI. That MI has some 
problems generics do not have is a big lie.

But in my view generics are beyond salvation. The idea is inherently 
weakly typed. Ada's generic contracts are too loose to be safe and too 
rigid for usability of C++ templates.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de