notmuch/bindings/ruby/defs.h, branch 0.39_rc2

ruby: db: reorganize initializer

2023-05-29T10:51:02Z

In order to make it more extensible. No functional changes. Signed-off-by: Felipe Contreras

ruby: remove FileNames object

2023-04-12T10:30:01Z

Not used anymore now that we return an array of strings directly. Signed-off-by: Felipe Contreras

ruby: add filenames helper

2023-04-12T10:05:23Z

Right now it doesn't do much, but it will help for further reorganization. Signed-off-by: Felipe Contreras

ruby: remove Tags object

2023-04-02T22:11:10Z

Not used anymore now that we return an array of strings directly. Signed-off-by: Felipe Contreras

ruby: add tags helper

2023-04-02T22:00:49Z

Right now it doesn't do much, but it will help for further reorganization. Signed-off-by: Felipe Contreras

ruby: cleanup object_destroy()

2021-08-03T23:30:15Z

It was assumed the destructor of notmuch_rb_database_type did return a notmuch_status_t because that's what notmuch_database_close returns, and that value was checked by notmuch_rb_database_close in order to decide if to raise an exception. It turns out notmuch_database_destroy was called instead, so nothing was returned (void). All the destroy functions are void, and that's what we want. Signed-off-by: Felipe Contreras

ruby: split database close and destroy

2021-08-02T16:49:29Z

Mirrors the C API: 7864350c (Split notmuch_database_close into two functions, 2012-04-25). Signed-off-by: Felipe Contreras

ruby: enable garbage collection using talloc

2021-07-18T20:08:53Z

We basically steal all the objects from their notmuch parents, therefore they are completely under Ruby's gc control. The order at which these objects are freed does not matter any more, because destroying the database does not destroy all the children objects, since they belong to Ruby now. Signed-off-by: Felipe Contreras

ruby: create an actual wrapper struct

2021-07-18T20:08:42Z

Currently Ruby data points directly to a notmuch object (e.g. notmuch_database_t), since we don't need any extra data that is fine. However, in the next commit we will need extra data, therefore we create a new struct notmuch_rb_object_t wrapper which contains nothing but a pointer to the current pointer (e.g. notmuch_database_t). This struct is tied to the Ruby object, and is freed when the Ruby object is freed by the garbage collector. We do nothing with this wrapper, so no functionality should be changed. Signed-off-by: Felipe Contreras

ruby: add keyword arguments to db.query

2021-06-27T17:13:03Z

That way we don't need pass them to the query object ourselves. Signed-off-by: Felipe Contreras