Hello,

we've just open sourced a small module ("accessors") that helps to generate getters and setters automatically:
https://github.com/funkwerk/accessors
http://code.dlang.org/packages/accessors

It takes advantage of the UDAs and mixins. A simple example would be:

import accessors;

class WithAccessors
{
    @Read @Write
    private int num_;

    mixin(GenerateFieldAccessors);
}

It would generate 2 methods "num": one to set num_ and one to get its value. Of cause you can generate only @Read without @Write and vice versa. There are some more features, you can find the full documentation in the README.
"GenerateFieldAccessors" mixin should be added into each class/struct that wants to use auto generated accessors.

On Friday, 9 December 2016 at 10:27:05 UTC, Eugene Wissner wrote:
> Hello,
>
> we've just open sourced a small module ("accessors") that helps to generate getters and setters automatically:
> https://github.com/funkwerk/accessors
> http://code.dlang.org/packages/accessors
>
> It takes advantage of the UDAs and mixins. A simple example would be:
>
> import accessors;
>
> class WithAccessors
> {
>     @Read @Write
>     private int num_;
>
>     mixin(GenerateFieldAccessors);
> }
>
> It would generate 2 methods "num": one to set num_ and one to get its value. Of cause you can generate only @Read without @Write and vice versa. There are some more features, you can find the full documentation in the README.
> "GenerateFieldAccessors" mixin should be added into each class/struct that wants to use auto generated accessors.

Is there possibility to remove affixes in generated accessor names?

mixin template GenerateFieldAccessorMethods()
{
    static enum GenerateFieldAccessorMethods()
    {
        string result = "";
        return result;
    }
}

Strange syntax

On Friday, 9 December 2016 at 12:37:58 UTC, Iakh wrote:
>
> Is there possibility to remove affixes in generated accessor names?

No, there is no way to manipulate the accessor names. What affixes do you mean?

On 12/9/16 5:27 AM, Eugene Wissner wrote:
> Hello,
>
> we've just open sourced a small module ("accessors") that helps to
> generate getters and setters automatically:
> https://github.com/funkwerk/accessors
> http://code.dlang.org/packages/accessors
>
> It takes advantage of the UDAs and mixins. A simple example would be:
>
> import accessors;
>
> class WithAccessors
> {
>     @Read @Write
>     private int num_;
>
>     mixin(GenerateFieldAccessors);
> }
>
> It would generate 2 methods "num": one to set num_ and one to get its
> value. Of cause you can generate only @Read without @Write and vice
> versa. There are some more features, you can find the full documentation
> in the README.
> "GenerateFieldAccessors" mixin should be added into each class/struct
> that wants to use auto generated accessors.

Love it, and was toying with similar ideas too. One good extension is to add a predicate to the setter, which guards the assignment. -- Andrei

On Friday, 9 December 2016 at 10:27:05 UTC, Eugene Wissner wrote:
> Hello,
>
> we've just open sourced a small module ("accessors") that helps to generate getters and setters automatically:
> https://github.com/funkwerk/accessors
> http://code.dlang.org/packages/accessors
>
> It takes advantage of the UDAs and mixins. A simple example would be:
>
> import accessors;
>
> class WithAccessors
> {
>     @Read @Write
>     private int num_;
>
>     mixin(GenerateFieldAccessors);
> }
>
> It would generate 2 methods "num": one to set num_ and one to get its value. Of cause you can generate only @Read without @Write and vice versa. There are some more features, you can find the full documentation in the README.
> "GenerateFieldAccessors" mixin should be added into each class/struct that wants to use auto generated accessors.

Oh my this is going to be a compiletime hog if used excessively.
Due the use of fqn.

On Friday, 9 December 2016 at 16:30:55 UTC, Eugene Wissner wrote:
> On Friday, 9 December 2016 at 12:37:58 UTC, Iakh wrote:
>>
>> Is there possibility to remove affixes in generated accessor names?
>
> No, there is no way to manipulate the accessor names. What affixes do you mean?

You can remove suffix "_" so "name_" becomes "name". But I like
to see genarated accessors "name" for field "m_name"

On Friday, 9 December 2016 at 10:27:05 UTC, Eugene Wissner wrote:
> It would generate 2 methods "num": one to set num_ and one to get its value.

It would be great if you could generate @properties instead. I like the more natural way of accessing those instead of getters/setters.

On Saturday, 10 December 2016 at 20:25:05 UTC, Mike Bierlee wrote:
> On Friday, 9 December 2016 at 10:27:05 UTC, Eugene Wissner wrote:
>> It would generate 2 methods "num": one to set num_ and one to get its value.
>
> It would be great if you could generate @properties instead. I like the more natural way of accessing those instead of getters/setters.

What are properties if not "getters" and "setters"? From the original post: "It would generate 2 methods "num": one to set num_ and one to get its value."

Two methods named "num". No "get" or "set" in sight.

On Sunday, 11 December 2016 at 02:17:18 UTC, Mike Parker wrote:
> On Saturday, 10 December 2016 at 20:25:05 UTC, Mike Bierlee wrote:
>> On Friday, 9 December 2016 at 10:27:05 UTC, Eugene Wissner wrote:
>>> It would generate 2 methods "num": one to set num_ and one to get its value.
>>
>> It would be great if you could generate @properties instead. I like the more natural way of accessing those instead of getters/setters.
>
> What are properties if not "getters" and "setters"? From the original post: "It would generate 2 methods "num": one to set num_ and one to get its value."
>
> Two methods named "num". No "get" or "set" in sight.

I was under the impression that you could only access methods as if they were fields using the @property attribute. After carefully reading the documentation I see this is not the case (UFCS does this). Still there are some added benefits from using @property to completely threat them as fields. It would be nice if you could add @property to the generated getters/setters.