Tarantool development patches archive
 help / color / mirror / Atom feed
From: Serge Petrenko <sergepetrenko@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 2/4] uuid: expose additional from_string constructors
Date: Fri, 10 Apr 2020 02:46:33 +0300	[thread overview]
Message-ID: <61D44098-8826-479E-A7F9-E1122410A057@tarantool.org> (raw)
In-Reply-To: <d749e0a6-56d8-d33f-f304-6a04607030f3@tarantool.org>

Hi! Thanks for the review!


> 6 апр. 2020 г., в 00:22, Vladislav Shpilevoy <v.shpilevoy@tarantool.org> написал(а):
> 
> Thanks for the patch!
> 
>> diff --git a/src/lib/uuid/tt_uuid.c b/src/lib/uuid/tt_uuid.c
>> index 1bd2e2cfe..94a0b15bb 100644
>> --- a/src/lib/uuid/tt_uuid.c
>> +++ b/src/lib/uuid/tt_uuid.c
>> @@ -65,6 +65,15 @@ tt_uuid_create(struct tt_uuid *uu)
>> }
>> #endif
>> 
>> +extern inline int
> 
> 'inline' modifier won't change anything. The function body is
> not visible anyway.

Not sure about that.
What about other functions?

```
extern inline int                                                                   
tt_uuid_from_string(const char *in, struct tt_uuid *uu);
```

I’m still not sure what ‘extern inline’ does, but I googled a stackoverflow
question discussing it:
https://stackoverflow.com/questions/216510/what-does-extern-inline-do

> 
>> +tt_uuid
>> _validate(struct tt_uuid *uu);
>> +
>> +extern inline int
>> +tt_uuid_from_fmt_string(const char *in, struct tt_uuid *uu, const char *fmt);
>> +
>> +extern inline int
>> +tt_uuid_from_lstring(const char *in, uint32_t len, struct tt_uuid *uu);
>> +
>> extern inline int
>> tt_uuid_from_string(const char *in, struct tt_uuid *uu);
>> 
> 
> There are unit tests for uuid in unit/uuid.c. You may need to
> add tests for the new functions.

I removed all the excess tt_uuid_from_* helpers in the new version after discussing
the patch with Mons. He is okay with allowing only cdata in indices, so I don’t need
the from string constructors anymore.

--
Serge Petrenko
sergepetrenko@tarantool.org

  reply	other threads:[~2020-04-09 23:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 23:02 [Tarantool-patches] [PATCH 0/4] introduce indices over UUID Serge Petrenko
2020-04-03 23:02 ` [Tarantool-patches] [PATCH 1/4] decimal: fix comment typo Serge Petrenko
2020-04-05 21:22   ` Vladislav Shpilevoy
2020-04-03 23:02 ` [Tarantool-patches] [PATCH 2/4] uuid: expose additional from_string constructors Serge Petrenko
2020-04-05 21:22   ` Vladislav Shpilevoy
2020-04-09 23:46     ` Serge Petrenko [this message]
2020-04-10 16:56       ` Vladislav Shpilevoy
2020-04-11 13:35         ` Serge Petrenko
2020-04-03 23:02 ` [Tarantool-patches] [PATCH 3/4] box: add MsgPack encoding/decoding for UUID Serge Petrenko
2020-04-05 21:26   ` Vladislav Shpilevoy
2020-04-09 23:46     ` Serge Petrenko
2020-04-03 23:02 ` [Tarantool-patches] [PATCH 4/4] box: introduce indices by UUID Serge Petrenko
2020-04-05 21:29   ` Vladislav Shpilevoy
2020-04-09 23:46     ` Serge Petrenko
2020-04-10 16:56       ` Vladislav Shpilevoy
2020-04-05 21:21 ` [Tarantool-patches] [PATCH 0/4] introduce indices over UUID Vladislav Shpilevoy
2020-04-09 23:46   ` Serge Petrenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=61D44098-8826-479E-A7F9-E1122410A057@tarantool.org \
    --to=sergepetrenko@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 2/4] uuid: expose additional from_string constructors' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox