- Apr 13, 2023
-
-
Rico Tzschichholz authored
-
- Apr 08, 2023
-
-
Rico Tzschichholz authored
-
- Sep 17, 2022
-
-
Rico Tzschichholz authored
-
If a chain of maps fails, the final `exception` should be the actual exception, not a semi-useless `FutureError.EXCEPTION`. Fixes #23
-
Rico Tzschichholz authored
-
- Aug 01, 2022
-
-
Rico Tzschichholz authored
-
- Apr 04, 2022
-
-
- Feb 10, 2022
-
-
Rico Tzschichholz authored
-
- Jan 30, 2022
-
-
Rico Tzschichholz authored
-
- Nov 30, 2021
-
-
Include Makefile.introspection instead of using a custom rule which will result in the following build failure when cross-compiling on buildroot because of missing --includedir: /home/giuliobenetti/autobuild/run/instance-1/output-1/host/bin/../riscv32-buildroot-linux-gnu/sysroot/usr/bin/g-ir-compiler -l `/usr/bin/sed -nE "s/^dlname='([A-Za-z0-9.+-]+)'/\1/p" libgee-0.8.la` -o Gee-0.8.typelib Gee-0.8.gir libgee-0.8.la Could not find GIR file 'GObject-2.0.gir'; check XDG_DATA_DIRS or use --includedir error parsing file Gee-0.8.gir: Failed to parse included gir GObject-2.0 Fixes: - http://autobuild.buildroot.org/results/884faa0f84c8dc43ed1ca6cde9caf21c731a4b35 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
-
- Oct 15, 2021
-
-
Rico Tzschichholz authored
-
- Mar 17, 2021
-
-
Rico Tzschichholz authored
-
- Mar 07, 2021
-
-
Rico Tzschichholz authored
-
- Feb 05, 2021
-
-
Rico Tzschichholz authored
-
- Oct 23, 2020
-
-
- Feb 09, 2020
-
-
Rico Tzschichholz authored
-
- Nov 25, 2019
-
-
Rico Tzschichholz authored
-
- Oct 05, 2019
-
-
Rico Tzschichholz authored
It is possible that a spurious or stolen wakeup could occur. For that reason, waiting on a condition variable should always be in a loop, based on an explicitly-checked predicate. Fixes #34
-
- Sep 25, 2019
-
-
Rico Tzschichholz authored
-
- Aug 05, 2019
-
-
Rico Tzschichholz authored
-
- Apr 01, 2019
-
-
Rico Tzschichholz authored
-
Rico Tzschichholz authored
-
Rico Tzschichholz authored
-
- Mar 14, 2019
-
-
Rico Tzschichholz authored
-
- Dec 16, 2018
-
-
Andre Klapper authored
-
Andre Klapper authored
-
Andre Klapper authored
-
- Feb 11, 2018
-
-
Maciej (Matthew) Piechotka authored
-
Maciej (Matthew) Piechotka authored
This reverts commit da95e830.
-
- Dec 11, 2017
-
-
* one_match (Predicate<G>) check if exactly one element matches * count_match (Predicate<G>) returns the count of items that matches https://bugzilla.gnome.org/show_bug.cgi?id=781641
-
Rico Tzschichholz authored
-
- Sep 12, 2017
-
-
Rico Tzschichholz authored
-
- Mar 21, 2017
-
-
Maciej (Matthew) Piechotka authored
-
- Feb 23, 2017
-
-
Maciej (Matthew) Piechotka authored
-
Maciej (Matthew) Piechotka authored
-
- Jan 17, 2017
-
-
* first_match (Predicate<G>) returns the first item that matches * any_match (Predicate<G>) checks if any element matches * all_match (Predicate<G>) checks if all elements match * max/min returns max/min value * order_by to perform ordering on any Traversable https://bugzilla.gnome.org/show_bug.cgi?id=776558
-
- Dec 14, 2016
-
-
Rico Tzschichholz authored
-
- Nov 23, 2016
-
-
Enumerations and flags are classed types for Vala, not integers, so they don't fall in the `typeof(G) == typeof(int)` kind of tests. This leads to using the generic code in which Vala assumes pointer-sized elements, which is often not true for enumerations and flags. Add special case for those to use the `int` converters for enumerations and flags. This is most generally correct, but not always: the compiler will likely chose a larger type for a specific enumeration if one of its value is larger than `int`. It would be tempting to use the enumeration's class minimum and maximum values to determine the appropriate type, but unfortunately the API for this uses int itself, so doesn't help. https://bugzilla.gnome.org/show_bug.cgi?id=774669
-
- Oct 12, 2016
-
-
Maciej (Matthew) Piechotka authored
-
Discussed this briefly with upstream on IRC, and it was concluded that this should probably have been forbidden by the Vala compiler in the first place. https://bugzilla.gnome.org/show_bug.cgi?id=772417
-