On Saturday, 16 March 2024 at 20:34:57 UTC, Inkrementator wrote:
Nice. Btw I vaguely remember you also wrote about how and why
to reduce the usage string mixins, with some real example of
alternative techniques you used
go to the main page: http://dpldocs.info/this-week-in-d/Blog.html
and
On Saturday, 16 March 2024 at 13:09:13 UTC, Adam D Ruppe wrote:
On Thursday, 14 March 2024 at 23:19:37 UTC, Inkrementator wrote:
@(__traits(getAttributes, thingYouWantToForward))
void yourNewThing() {}
Thanks, that should solve my problem.
On Friday, 15 March 2024 at 19:13:38 UTC, cc wrote:
This is trivially easy if your types are visible at module
level, and mixin is a fine tool for the job. It doesn't work
quite so well with [Voldemort
types](https://wiki.dlang.org/Voldemort_types).
I used the following lines to make it work
On Thursday, 14 March 2024 at 23:19:37 UTC, Inkrementator wrote:
* Is UDA propagation possible without string mixins?
@(__traits(getAttributes, thingYouWantToForward))
void yourNewThing() {}
* Are template mixins vulnerable to name collisions?
On Thursday, 14 March 2024 at 23:19:37 UTC, Inkrementator wrote:
I am trying to derive a struct from another. I want to modify
each field such that type of it goes from some T to Nullable!T,
preserving all fieldnames and UDAs.
This is trivially easy if your types are visible at module level,
Hello,
I am trying to derive a struct from another. I want to modify
each field such that type of it goes from some T to Nullable!T,
preserving all fieldnames and UDAs.
I think that fieldnames and UDAs can only be duplicated via
string-mixins. This means that all field-types that aren't
