Not really. Part of the point of voldemort types is that no information about the type is 'leaked' outside the function. In this case, the trait 'HasGetValue' is leaked and can be used by other code.
When would you want to have an interface such that nothing about the return type of a function is known to the outside world? I'm genuinely asking; I just don't understand the utility of this concept.
Re:The Vale Programming Language
by mumblemumble on Friday November 20, 2020 @06:32PM
(#25166432)
I don't think anyone's trying to argue about whether it's better or worse than the Rust concept. Just that it's subtly different.
I'm not interested in comparing it to the rust concept. I'm just curious why this is something people find valuable in D, and why another commenter would call it a feature D "would be ruined without"
Re:The Vale Programming Language
by bobthebuilders on Saturday November 21, 2020 @02:20AM
(#25168323)
The commentor is just mistaken. The two do the exact same thing.
Note that interfaces in Rust are not types, they do not name types. A value cannot have interface type. What happens when you return an “impl” type is that you return some unspecified type, but that type must implement the specified interface.
You could translate the D example to:
The “create_voldemort_type” function simply returns a value of unspecified type. As far as I can tell, this is equivalent to the D code, except it doesn’t use type inference for the function type.