Re: Off-Band Discussion with @muellerr: I think index needs to be checked for nullptr (and my younger self needs a stern talking to for writing uint8_t *index = 0 without this check), as the interface presents nullptr as a valid choice.
Regarding checking vector and size, the whole module does not do nullptr/size checks. I am not sure whether to keep it that way or refactor it to checking and returning Returnvalue_t.
I think the idea in the first place was to keep the interface slim, to not bloat math code, which is a debatable argument...
nice catch @meggert !
Re: Off-Band Discussion with @muellerr: I think `index` needs to be checked for `nullptr` (and my younger self needs a stern talking to for writing `uint8_t *index = 0` without this check), as the interface presents `nullptr` as a valid choice.
Regarding checking `vector` and `size`, the whole module does not do `nullptr`/size checks. I am not sure whether to keep it that way or refactor it to checking and returning `Returnvalue_t`.
I think the idea in the first place was to keep the interface slim, to not bloat math code, which is a debatable argument...
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
nice catch @meggert !
Re: Off-Band Discussion with @muellerr: I think
indexneeds to be checked fornullptr(and my younger self needs a stern talking to for writinguint8_t *index = 0without this check), as the interface presentsnullptras a valid choice.Regarding checking
vectorandsize, the whole module does not donullptr/size checks. I am not sure whether to keep it that way or refactor it to checking and returningReturnvalue_t.I think the idea in the first place was to keep the interface slim, to not bloat math code, which is a debatable argument...