dnf5/bindings
Aleš Matěj 141dabd943 Copy return value from `SetConstIterator::operator*`
`SetConstIterator::operator*` returns a reference, this is visible in
cpp and the user behaves accordingly.

In Python the user expects automatic memory management, the object
returned from query iterator should be valid as long as there is a
reference to it.
To ensure this add swig typemaps that copy the returned object.
It works because none of the queries (RepoQeury, GroupQuery,
EnvironmentQuery) store the actual data. They just store some kind of
proxy (RepoWeakPtr or wrapped libsolv ids) so if we copy the RepoWeakPtr
it still points to the same Repo object.

The PackageQuery and AdvisoryQuery return by value even in cpp so they
don't have this problem.
2025-07-24 06:53:45 +00:00
..
go CMake: Use list(APPEND FOO) over set(FOO ${FOO} ...) 2025-02-17 09:38:01 +00:00
libdnf5 Copy return value from `SetConstIterator::operator*` 2025-07-24 06:53:45 +00:00
libdnf5_cli libdnf5-cli library: Do not export private symbols 2024-06-10 09:54:06 +00:00
perl5 Fix misspellings 2024-01-15 09:54:08 +00:00
python3 CMake: Use list(APPEND FOO) over set(FOO ${FOO} ...) 2025-02-17 09:38:01 +00:00
ruby Fix clang build by disabling ruby deprecation warning 2025-05-14 11:53:01 +00:00
CMakeLists.txt SWIG: Implement exception forwarding 2025-04-04 05:37:55 +00:00