Several objects implemented their own uint property getters and setters,
despite them being straightforward (without any checks/validations on
the values themselves) and identical across objects. This makes use of
an enhanced API for object_property_add_uintXX_ptr() which offers
default setters.
S
> On Nov 27, 2019, at 11:58 PM, Alexey Kardashevskiy wrote:
>
>
>
> On 26/11/2019 20:39, Felipe Franciosi wrote:
>>
>>
>>> On Nov 26, 2019, at 8:39 AM, Marc-André Lureau
>>> wrote:
>>>
>>> Hi
>>
>> Heya, thanks for the review.
>>
>>>
>>> On Mon, Nov 25, 2019 at 7:37 PM Felipe Francios
On 26/11/2019 20:39, Felipe Franciosi wrote:
>
>
>> On Nov 26, 2019, at 8:39 AM, Marc-André Lureau
>> wrote:
>>
>> Hi
>
> Heya, thanks for the review.
>
>>
>> On Mon, Nov 25, 2019 at 7:37 PM Felipe Franciosi wrote:
>>>
>>> Several objects implemented their own uint property getters and se
> On Nov 26, 2019, at 8:39 AM, Marc-André Lureau
> wrote:
>
> Hi
Heya, thanks for the review.
>
> On Mon, Nov 25, 2019 at 7:37 PM Felipe Franciosi wrote:
>>
>> Several objects implemented their own uint property getters and setters,
>> despite them being straightforward (without any check
Hi
On Mon, Nov 25, 2019 at 7:37 PM Felipe Franciosi wrote:
>
> Several objects implemented their own uint property getters and setters,
> despite them being straightforward (without any checks/validations on
> the values themselves) and identical across objects. This makes use of
> an enhanced AP
Several objects implemented their own uint property getters and setters,
despite them being straightforward (without any checks/validations on
the values themselves) and identical across objects. This makes use of
an enhanced API for object_property_add_uintXX_ptr() which offers
default setters.
S