Re: class wide iterable (and indexable)

[George Shapovalov <gshapovalov@gmail.com>]

On Saturday, January 5, 2019 at 9:07:10 PM UTC+1, Simon Wright wrote:
> George Shapovalov <gshapovalov@gmail.com> writes:
> > Is this something already well known or should I report this bug to
> > AdaCore?
> I think you should submit it. This is an ICE, should be of interest to
> AdaCore 
Ok, then I'll try to go about submitting it tomorrow (its getting late here today already).

> even if the circumstances are unusual!
Not for me :). This is far from the first gnat bug incidence I observe. One time it was even much weirder - first it started spitting out compilation error messages with clearly misplaced line of code references (off by a few lines, within the block unreachable by the quoted problematic line), and finally gave up and went down with another gnat bug message when pushed a bit more. At the time, IIRC, I was making another attempt to tie different type hierarchies together (and I remember child packages affected gnat stability too, compared to when I tried to pull them all together in one big package instead) while trying to absolutely avoid any code duplication. Similar to what Dmitry was describing here in this thread only instead of heavy generics use I was (ab)using interfaces..
But that was already a few years ago, on a much older gnat version (based around gcc-4 I think) with both FSF and ACT gnat rather in flux at the moment. So I doubt it makes sense at present to try to dig up that code.

So, I'll just submit this bug, as it concerns present gnat version (dev-lang/gnat-2018-r1 based on gcc-7.3.1 backend).