Re: Next steps of approved DIPs
On Wednesday, 20 February 2019 at 11:52:35 UTC, Peter Particle wrote: In particular I am interested in DIP 1014 but this question can be applied to any approved DIP. Where do I get information about e.g. implementer, implementation state/progress, which DMD version is expected to include it (apparently not 2.0.85), etc.? Normally the DIP author should be on top of that. Any time that's not the case, you can contact me directly and I'll see what's up. I'll see what's up with 1014 and reply here if someone involved doesn't get to it first.
Next steps of approved DIPs
In particular I am interested in DIP 1014 but this question can be applied to any approved DIP. Where do I get information about e.g. implementer, implementation state/progress, which DMD version is expected to include it (apparently not 2.0.85), etc.?
Qualifying function parameters using return vs return scope
Can somebody explain when - a free function parameter or - a struct/class member function's `this`-parameter should be qualified as `return` vs `return scope`? Is there a part of the spec that explains this difference? Further, are there differences in the way - a free function parameter, - a `struct` member function's `this` pointer, or - a `class` member function's `this` pointer is handled? I've noticed cases where using the `return scope` instead of just `return` prevents -dip1000 from detecting invalid escaping of scoped objects. Is this intended or a bug?
Re: Best practices of using const
On 20.02.2019 11:05, Kagamin wrote: On Tuesday, 19 February 2019 at 16:38:17 UTC, drug wrote: The same I can say about properties - for example I use them in meta programming to detect what to serialize/process - I skip methods but serialize properties and for me this is a nice language feature. Serialization of arbitrary stuff is a bad practice anyway, it was the cause of vulnerabilities in serialization libraries. DTO is the way to go. serialization is just an example here. But using properties lets me to avoid using DTO except really complex cases and lets me decrease maintenance cost. In my case (I develop a prototype and very often change its data structures) they work really well.
Re: Best practices of using const
On Tuesday, 19 February 2019 at 16:38:17 UTC, drug wrote: The same I can say about properties - for example I use them in meta programming to detect what to serialize/process - I skip methods but serialize properties and for me this is a nice language feature. Serialization of arbitrary stuff is a bad practice anyway, it was the cause of vulnerabilities in serialization libraries. DTO is the way to go.
