digitalmars.D - Naming Voldemort Types
- =?UTF-8?B?Ik5vcmRsw7Z3Ig==?= (8/8) Jun 25 2015 I've noticed that the namings of lazy range voldemort types are
- Steven Schveighoffer (5/12) Jun 25 2015 I think the actual name you use for a voldemort type is of no
- "Per =?UTF-8?B?Tm9yZGzDtnci?= <per.nordlow gmail.com> (3/5) Jun 25 2015 That doesn't sound like too hard to implement... :)
- Andrei Alexandrescu (2/9) Jun 25 2015 Result. No stuttering please. -- Andrei
- Walter Bright (4/15) Jun 25 2015 Also, consider that the mangled name includes the parent algorithm name....
- Jonathan M Davis (6/13) Jun 25 2015 It makes sense when we've been forced to make it so that the type
- Tofu Ninja (2/10) Jun 25 2015 I always name my Voldemort Types tomRiddle...
I've noticed that the namings of lazy range voldemort types are inconsistent in Phobos. Some are named `XResult` others just `Result`, given that `x` is the parenting algorithm. What's the policy here? I would prefer the verbose `XResult` as it's more self documenting when debugging or using for instance pragma(msg, typeof(r)) where `r` is an instance of a lazy range. What do you guys think?
Jun 25 2015
On 6/25/15 9:12 AM, "Nordlöw" wrote:I've noticed that the namings of lazy range voldemort types are inconsistent in Phobos. Some are named `XResult` others just `Result`, given that `x` is the parenting algorithm. What's the policy here? I would prefer the verbose `XResult` as it's more self documenting when debugging or using for instance pragma(msg, typeof(r)) where `r` is an instance of a lazy range. What do you guys think?I think the actual name you use for a voldemort type is of no importance. I would like to see pragma(msg, typeof(r)) print something like functionThatReturnsVoldemort.Result -Steve
Jun 25 2015
On Thursday, 25 June 2015 at 13:59:14 UTC, Steven Schveighoffer wrote:iI would like to see pragma(msg, typeof(r)) print something like functionThatReturnsVoldemort.ResultThat doesn't sound like too hard to implement... :)
Jun 25 2015
On 6/25/15 6:12 AM, "Nordlöw" wrote:I've noticed that the namings of lazy range voldemort types are inconsistent in Phobos. Some are named `XResult` others just `Result`, given that `x` is the parenting algorithm. What's the policy here? I would prefer the verbose `XResult` as it's more self documenting when debugging or using for instance pragma(msg, typeof(r)) where `r` is an instance of a lazy range. What do you guys think?Result. No stuttering please. -- Andrei
Jun 25 2015
On 6/25/2015 11:54 AM, Andrei Alexandrescu wrote:On 6/25/15 6:12 AM, "Nordlöw" wrote:Also, consider that the mangled name includes the parent algorithm name. Let's not make mangled names excessively large, even if it is an implementation problem that we should address on its own anyway.I've noticed that the namings of lazy range voldemort types are inconsistent in Phobos. Some are named `XResult` others just `Result`, given that `x` is the parenting algorithm. What's the policy here? I would prefer the verbose `XResult` as it's more self documenting when debugging or using for instance pragma(msg, typeof(r)) where `r` is an instance of a lazy range. What do you guys think?Result. No stuttering please. -- Andrei
Jun 25 2015
On Thursday, 25 June 2015 at 20:58:41 UTC, Walter Bright wrote:On 6/25/2015 11:54 AM, Andrei Alexandrescu wrote:It makes sense when we've been forced to make it so that the type isn't actually Voldemort type (e.g. FilterResult is a private struct outside of filter), but when it's actually a Voldemort type, Result should work just fine. - Jonathan M DavisResult. No stuttering please. -- AndreiAlso, consider that the mangled name includes the parent algorithm name. Let's not make mangled names excessively large, even if it is an implementation problem that we should address on its own anyway.
Jun 25 2015
On Thursday, 25 June 2015 at 13:12:18 UTC, Nordlöw wrote:I've noticed that the namings of lazy range voldemort types are inconsistent in Phobos. Some are named `XResult` others just `Result`, given that `x` is the parenting algorithm. What's the policy here? I would prefer the verbose `XResult` as it's more self documenting when debugging or using for instance pragma(msg, typeof(r)) where `r` is an instance of a lazy range. What do you guys think?I always name my Voldemort Types tomRiddle...
Jun 25 2015