aBothe/Mono-D — Issue #42: code completion for nested types not ideal
Author: jpf91
Created: 2012-02-02 16:55:35+00:00
State: open

With this example code:

```d
public struct UUID
{
public:
/**
* These are the UUID formats supported by this module. It's
* possible to read, compare and use all these Variants, but
* UUIDs generated by this module will always be in rfc4122 format.
*/
enum Variant
{
ncs, /// NCS backward compatibility
rfc4122, /// defined in RFC 4122 document
microsoft, /// Microsoft Corporation backward compatibility
future ///reserved for future use
}
}

```

Variant doesn't show up in the code completion popup if you type "UUID.", but it does show up if you type "UUID instance; instance.". It should behave exactly the opposite way. If Variant is written like this though "static enum Variant", it works correctly. This might make sense for nested classes(I'm not sure about structs, do nested structs have a reference to their parent class/struct?), but I think enums are always static.

BTW: Mono-D is really awesome. If only more distributions had recent monodevelop packages (I'm using debian testing and had to install all mono packages from unstable. Not nice, but everything works fine)

BTW2: The bug tracker could use some labels (enhancement, crash, featureRequest, bug, ...)