Merge pull request #188 from gtk-rs/create-pull-request/patch

Update GIR files (2024-02-09)

GLib-2.0.gir

@@ -44010,7 +44010,11 @@ threads are using the same datalist and the same key.</doc>
       <doc xml:space="preserve">Removes multiple keys from a datalist.
 
 This is more efficient than calling g_datalist_id_remove_data()
-multiple times in a row.</doc>
+multiple times in a row.
+
+Before 2.80, @n_keys had to be not larger than 16. Now it can be larger, but
+note that GData does a linear search, so an excessive number of keys will
+perform badly.</doc>
       <return-value transfer-ownership="none">
         <type name="none" c:type="void"/>
       </return-value>
@@ -44026,7 +44030,7 @@ multiple times in a row.</doc>
           </array>
         </parameter>
         <parameter name="n_keys" transfer-ownership="none">
-          <doc xml:space="preserve">length of @keys, must be &lt;= 16</doc>
+          <doc xml:space="preserve">length of @keys.</doc>
           <type name="gsize" c:type="gsize"/>
         </parameter>
       </parameters>
@@ -55961,12 +55965,13 @@ g_test_init(), the option `-m perf` enables performance tests, while
 `-m quick` disables them.</doc>
     </function-macro>
     <function name="test_queue_destroy" c:identifier="g_test_queue_destroy" version="2.16">
-      <doc xml:space="preserve">This function enqueus a callback @destroy_func to be executed
-during the next test case teardown phase. This is most useful
-to auto destruct allocated test resources at the end of a test run.
-Resources are released in reverse queue order, that means enqueueing
-callback A before callback B will cause B() to be called before
-A() during teardown.</doc>
+      <doc xml:space="preserve">Enqueues a callback @destroy_func to be executed during the next test case
+teardown phase.
+
+This is most useful to auto destroy allocated test resources at the end of a
+test run. Resources are released in reverse queue order, that means
+enqueueing callback `A` before callback `B` will cause `B()` to be called
+before `A()` during teardown.</doc>
       <return-value transfer-ownership="none">
         <type name="none" c:type="void"/>
       </return-value>

Gdk-4.0.gir

@@ -4072,6 +4072,7 @@ virtualized test environments.</doc>
         <type name="gboolean" c:type="gboolean"/>
       </property>
       <property name="dmabuf-formats" version="4.14" transfer-ownership="none" getter="get_dmabuf_formats">
+        <attribute name="org.gtk.Property.get" value="gdk_display_get_dmabuf_formats"/>
         <doc xml:space="preserve">The dma-buf formats that are supported on this display</doc>
         <type name="DmabufFormats"/>
       </property>
@@ -4347,6 +4348,24 @@ Note that DMA buffers only exist on Linux.</doc>
           </parameter>
         </parameters>
       </method>
+      <method name="equal" c:identifier="gdk_dmabuf_formats_equal" version="4.14">
+        <doc xml:space="preserve">Returns whether @formats1 and @formats2 contain the
+same dmabuf formats, in the same order.</doc>
+        <return-value transfer-ownership="none">
+          <doc xml:space="preserve">`TRUE` if @formats1 and @formats2 are equal</doc>
+          <type name="gboolean" c:type="gboolean"/>
+        </return-value>
+        <parameters>
+          <instance-parameter name="formats1" transfer-ownership="none" nullable="1" allow-none="1">
+            <doc xml:space="preserve">a `GdkDmabufFormats`</doc>
+            <type name="DmabufFormats" c:type="const GdkDmabufFormats*"/>
+          </instance-parameter>
+          <parameter name="formats2" transfer-ownership="none" nullable="1" allow-none="1">
+            <doc xml:space="preserve">another `GdkDmabufFormats`</doc>
+            <type name="DmabufFormats" c:type="const GdkDmabufFormats*"/>
+          </parameter>
+        </parameters>
+      </method>
       <method name="get_format" c:identifier="gdk_dmabuf_formats_get_format" version="4.14">
         <doc xml:space="preserve">Gets the fourcc code and modifier for a format
 that is contained in @formats.</doc>
@@ -4420,7 +4439,7 @@ the object is freed.</doc>
       </method>
     </record>
     <class name="DmabufTexture" c:symbol-prefix="dmabuf_texture" c:type="GdkDmabufTexture" version="4.14" parent="Texture" glib:type-name="GdkDmabufTexture" glib:get-type="gdk_dmabuf_texture_get_type" glib:type-struct="DmabufTextureClass">
-      <doc xml:space="preserve">A `GdkTexture` representing a dma-buf object.
+      <doc xml:space="preserve">A `GdkTexture` representing a DMA buffer.
 
 To create a `GdkDmabufTexture`, use the auxiliary
 [[email protected]] object.

Gio-2.0.gir

@@ -76705,9 +76705,18 @@ This is a variant of g_task_set_name() that avoids copying @name.</doc>
       </method>
       <property name="completed" version="2.44" transfer-ownership="none" getter="get_completed" default-value="FALSE">
         <doc xml:space="preserve">Whether the task has completed, meaning its callback (if set) has been
-invoked. This can only happen after g_task_return_pointer(),
+invoked.
+
+This can only happen after g_task_return_pointer(),
 g_task_return_error() or one of the other return functions have been called
-on the task.
+on the task. However, it is not guaranteed to happen immediately after
+those functions are called, as the task&#x2019;s callback may need to be scheduled
+to run in a different thread.
+
+That means it is **not safe** to use this property to track whether a
+return function has been called on the #GTask. Callers must do that
+tracking themselves, typically by linking the lifetime of the #GTask to the
+control flow of their code.
 
 This property is guaranteed to change from %FALSE to %TRUE exactly once.