On Tue, Apr 10, 2018 at 12:24 PM, Pavel Labath via Dwarf-Discuss
wrote:
> namespace namesp1 { int var; }
> namespace namesp2 = namesp1; // DW_TAG_imported_declaration
A namespace alias like this should certainly be represented. I'm not
sure about other uses of
I have nothing to add to what Paul just said :)
This is definitely the intent and what we should do.
-eric
On Tue, Apr 10, 2018 at 10:26 AM Paul Robinson via Dwarf-Discuss <
dwarf-discuss@lists.dwarfstd.org> wrote:
> The intent of the index is given pretty plainly in the non-normative text
>
The intent of the index is given pretty plainly in the non-normative text at
the bottom of p.137; you should be able to look up any unqualified name in the
index. If the normative text doesn't accomplish that, we have an opportunity
to improve the spec. ☺
FWIW here's my take:
Enumerations
Yep - sounds like it to me.
I suppose, arguably, one could say that successful name lookups of things
in the index can be fast, while lookups that fail, or find names not in the
index may be slow - but that seems unacceptable to me (in many cases "slow"
would be "prohibitively slow" especially
On 04/10/2018 08:33 AM, Pavel Labath via Dwarf-Discuss wrote:
I believe it makes sense to include both of these things in the index
(including the implicitly-named imported declarations), however I would
also like to stick to the specification as much as possible. I know the
spec gives
On Tue, 10 Apr 2018 at 16:44, David Blaikie wrote:
> I'd say any case where a consumer couldn't actually rely on the table to
> do name resolution would be a bug - or at least something that needs to be
> seriously considered/discussed/figured out how the name table can be